Several chilli process in the same computer

wlan at mac.com wlan at mac.com
Thu May 15 17:31:40 UTC 2008


Chilli originally only had the uamport, and still does. uamuiport was  
added to allow a bit more ability (like POST processing) for the  
embedded http server. While uamport binds to the uamlisten, currently  
uamuiport does not - it binds to '*' and thus must be different (or  
not used) with multiple instances. Perhaps it should just bind to  
uamlisten...

David


On May 15, 2008, at 4:08 PM, Krnák János wrote:

> hi
>
> there is also another option called uamuiport i think this is what  
> is used by the other chilli, change this as well
>
> bye
>
> Oguzhan Kayhan escribió:
>>
>>> I've created different config files but It doesn't work.  I use vlan
>>> interfaces, eth1.1, eth1.2 and eth1.3.  Do you use different  
>>> physical
>>> interfaces?  And I've got only one WAN interface, eth0.
>>>
>>> Thanks.
>>>
>>>
>> Actually, i am using both vlan interfaces and physical interfaces  
>> in my
>> network.
>>
>>
>> here's my ps-ef result for chilli.
>> be careful about selecting different pid files for chilli processes.
>> That might be your problem.
>>
>>
>> root     26032     1 16 May13 ?        08:00:31 /usr/sbin/chilli
>> --conf=/etc/chilli.d/chilli-dogu.conf --pidfile=/var/run/chilli- 
>> dogu.pid
>> root     26042     1  1 May13 ?        00:31:12 /usr/sbin/chilli
>> --conf=/etc/chilli.d/chilli-dogu-wireless.conf
>> --pidfile=/var/run/chilli-dogu-wireless.pid
>>
>>
>> We also made a modification in distrto package as we are keeping   
>> config
>> files under /etc/chilli.d/ folder
>> and all cofig files added to this folder runs a different chilli  
>> process.
>>
>>
>> Im also adding our init.d script for chilli in here for your test  
>> purposes.
>>
>> --------------------------------------------------------------------- 
>> ----
>>
>> PATH=/sbin:/bin:/usr/sbin:/usr/bin
>> DAEMON=/usr/sbin/chilli
>> NAME=chilli
>> DESC=chilli
>>
>> test -f $DAEMON || exit 0
>>
>> set -e
>>
>> case "$1" in
>>   start)
>>         echo -n "Starting $DESC: "
>>         if [ -d /etc/chilli.d ]; then
>>                 for cnf in /etc/chilli.d/*.conf
>>                 do
>>                         pfile=`basename $cnf .conf`
>>                         start-stop-daemon --start --quiet \
>>                                 --pidfile /var/run/$pfile.pid \
>>                                 --exec $DAEMON -- --conf=$cnf
>> --pidfile=/var/run/$pfile.pid
>>                         echo -n $pfile ", "
>>                 done
>>         else
>>                 start-stop-daemon --oknodo --stop --quiet --pidfile
>> /var/run/$NAME.pid \
>>                         --exec $DAEMON
>>         fi
>>         echo "$NAME."
>>         ;;
>> stop)
>>         echo -n "Stopping $DESC: "
>>         if [ -d /etc/chilli.d ]; then
>>                 for cnf in /etc/chilli.d/*.conf
>>                 do
>>                         pfile=`basename $cnf .conf`
>>                         start-stop-daemon --oknodo --stop --quiet \
>>                                 --pidfile /var/run/$pfile.pid \
>>                                 --exec $DAEMON -- --conf=$cnf
>>                         echo -n $pfile ", "
>>                 done
>>         else
>>                 start-stop-daemon --oknodo --stop --quiet --pidfile
>> /var/run/$NAME.pid \
>>                 --exec $DAEMON
>>         fi
>>         echo "$NAME."
>>         ;;
>>   #reload)
>> #reload)
>>         #
>>         #       If the daemon can reload its config files on the fly
>>         #       for example by sending it SIGHUP, do it here.
>>         #
>>         #       If the daemon responds to changes in its config file
>>         #       directly anyway, make this a do-nothing entry.
>>         #
>>         # echo "Reloading $DESC configuration files."
>>         # start-stop-daemon --stop --signal 1 --quiet --pidfile \
>>         #       /var/run/$NAME.pid --exec $DAEMON
>>   #;;
>>   restart|force-reload)
>>         #
>>         #       If the "reload" option is implemented, move the
>> "force-reload"
>>         #       option to the "reload" entry above. If not, "force- 
>> reload" is
>>         #       just the same as "restart".
>>         #
>>         echo -n "Restarting $DESC: "
>>         start-stop-daemon --stop --quiet --pidfile \
>>                 /var/run/$NAME.pid --exec $DAEMON
>>         sleep 1
>>         start-stop-daemon --start --quiet --pidfile \
>>            /var/run/$NAME.pid --exec $DAEMON
>>         echo "$NAME."
>>         ;;
>>   *)
>>         N=/etc/init.d/$NAME
>>         # echo "Usage: $N {start|stop|restart|reload|force- 
>> reload}" >&2
>>         echo "Usage: $N {start|stop|restart|force-reload}" >&2
>>         exit 1
>>         ;;
>> esac
>>
>> exit 0
>>
>> --------------------------------------------------------------------- 
>> ------------------
>>
>>
>>> Oguzhan Kayhan escribió:
>>>
>>>> Hello,
>>>> If you create different config files for chilli processes and  
>>>> set them
>>>> to
>>>> work on different interfaces, it should work without a  
>>>> problem..which
>>>> for
>>>> ex we use over 3-4 different interfaces with different chilli  
>>>> processes.
>>>>
>>>>
>>>>
>>>>> Hi list,
>>>>> is it possible to run several chilli process in the same  
>>>>> computer?.
>>>>> I'd
>>>>> like to do that so that I could set up different captive  
>>>>> portals for
>>>>> several interfaces in differents vlans.  But I get this error  
>>>>> debugging
>>>>> when I start the second process, although I use another uam  
>>>>> port, uam
>>>>> listen ip, pid file, sock file and ip range for this process.
>>>>>
>>>>> redir.c: 932: 0 (Debug) UAM port already in use. Waiting for  
>>>>> retry.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Javier
>>>>>
>>>>> ------------------------------------------------------------------ 
>>>>> ---
>>>>> To unsubscribe, e-mail: chilli-unsubscribe at coova.org
>>>>> For additional commands, e-mail: chilli-help at coova.org
>>>>> Wiki: http://coova.org/wiki/index.php/CoovaChilli
>>>>> Forum: http://coova.org/phpBB3/viewforum.php?f=4
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ------------------------------------------------------------------- 
>>>> --
>>>> To unsubscribe, e-mail: chilli-unsubscribe at coova.org
>>>> For additional commands, e-mail: chilli-help at coova.org
>>>> Wiki: http://coova.org/wiki/index.php/CoovaChilli
>>>> Forum: http://coova.org/phpBB3/viewforum.php?f=4
>>>>
>>>>
>>>>
>>>>
>>> -------------------------------------------------------------------- 
>>> -
>>> To unsubscribe, e-mail: chilli-unsubscribe at coova.org
>>> For additional commands, e-mail: chilli-help at coova.org
>>> Wiki: http://coova.org/wiki/index.php/CoovaChilli
>>> Forum: http://coova.org/phpBB3/viewforum.php?f=4
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: chilli-unsubscribe at coova.org
>> For additional commands, e-mail: chilli-help at coova.org
>> Wiki: http://coova.org/wiki/index.php/CoovaChilli
>> Forum: http://coova.org/phpBB3/viewforum.php?f=4
>>
>>
>>
>
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.  
> ---------------------------------------------------------------------  
> To unsubscribe, e-mail: chilli-unsubscribe at coova.org For additional  
> commands, e-mail: chilli-help at coova.org Wiki: http://coova.org/wiki/ 
> index.php/CoovaChilli Forum: http://coova.org/phpBB3/viewforum.php?f=4

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.coova.org/pipermail/chilli/attachments/20080515/f896501d/attachment.htm>


More information about the Chilli mailing list