[Chilli] chilli issues

David Bird david at coova.com
Thu Jun 3 04:36:20 UTC 2010

> * if you run multiple instance of chilli they happily all use the same
>    ipc file without giving any warning, with bad results

Don't do that..

> * if you configure the ipc filename with a full path, like you do for
>    all other filename options, the option is silently ignored

Then fix the config...

> * if the ethers file contains a comment or anything else the parser does
>    not like you get a single message in the debug output and the file is
>    otherwise silently ignored

Thanks for the patch.

> * I thought there was an option to use an ethers file and automatically
>    authenticate all MAC addresses in it. Currently you have to fake this
>    by listing the MAC address in macallowed and in a users file with a
>    dummy password (and in ethers as well if you want a static IP). This
>    is awkward

Not a feature, use MAC authentication. 

> * I have been completely unable to get MAC auth working using
>    macallowed and a users file and had to resorting to a script to run
>    a bunch of chilli_query commands on startup.

Use RADIUS (though the users file should work too).

> * if you do "chilli_query list -s <socket>" you get the output from all
>    chilli instances on a server without any kind of warning or header
>    indicating you are looking at multiple servers at once. This had me
>    extremely confused for a while.

The socket option has to come first, in fact it can optionally be the
first argument too (as in "chilli_query /path/to/socket list"

> I suspect most if not all of these are easy to fix. I've already taken a 
> stab at handling comments in the ethers file (commited, but untested 
> since I ran out of time). I'm hoping David can follow up on the others.

I'm busy too, but will review your changes. Patches are welcome,
especially the tested kind. 


More information about the Chilli mailing list