aboutsummaryrefslogtreecommitdiff
path: root/net/coova-chilli/files/chilli.init
Commit message (Collapse)AuthorAge
* coova-chilli: add interface_trigger "wan"Thibaut VARÈNE2022-01-29
| | | | | | | | | | | | This intends to replace the hotplug script. It still hardcodes "wan" interface name (as several other packages do) for lack of a deterministic way to detect the actual wan iface before it is brought up, but at least it is fully integrated with procd and will not start a disabled service. The interface trigger forcefully restarts chilli as a simple reload may not be sufficient to recover from wan changes. Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org>
* coova-chilli: execute firewall cleanup at shutdownThibaut VARÈNE2022-01-29
| | | | | | | | | | | Coova Chilli creates "undo" firewall scripts that are intended to be run when the daemon is shut down. Failure to do so results in leftover entries in firewall and duplicated ones if chilli is subsequently restarted. Execute these scripts when the service stops. Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org>
* coova-chilli: postpone startup until wan is availableThibaut VARÈNE2022-01-29
| | | | | | | | | Coova Chilli will fail to start if e.g. it cannot resolve names in its configuration (like uamserver, radiusserver, etc) which is typically the case when wan is unavailable. Prevent this situation by delaying startup if wan is not available. Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org>
* coova-chilli: enable service by defaultSungbo Eo2020-01-03
| | | | | | | | If "disabled" option does not exist, service should be enabled. Fixes: #10392 Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* coova-chilli: Fix debug flag config example and synchronize bool optionsPetr Štetiar2019-09-25
| | | | | | | | | | debug is boolean option/flag so setting it to 9 doesn't work, while at it I've synchronized boolean options from source code and sorted it alphabeticaly with following command: grep flag src/cmdline.ggo | cut -d \" -f2 | sort | tr '\n' '|' Signed-off-by: Petr Štetiar <ynezz@true.cz>
* coova-chilli: Fix unwanted startup of disabled instancesPetr Štetiar2019-09-25
| | | | | | | | | | | | Code in option_cb was referencing $chilli_inst variable which was declared as local, thus the instance startup logic in start_chilli was referencing variable which would always get value of 1, effectively making `disabled` config option useless. So I've fixed it with simpler config_get_bool and while at it, I've simplified the surrounding code little bit as well. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* coova-chilli: Wrap excessively long linesPetr Štetiar2019-09-25
| | | | Signed-off-by: Petr Štetiar <ynezz@true.cz>
* coova-chilli: switch to procdJaehoon You2018-04-23
| | | | Signed-off-by: Jaehoon You <teslamint@gmail.com>
* coova-chilli: Fix removal of old filesRajan Vaja2016-08-04
| | | | | | | | | | | | | | | | | Before starting chilli instance, it first removes generated files (/var/run/chilli*) for the instance. While deleting generated files, it doesn't match full instance name. Thus if coova-chilli config file (/etc/config/chilli) has instances wlan11 and wlan1 in order, when creating coova-chilli instance for wlan1, it is removing files generated for wlan11 instances also (as it uses wlan1* in remove command). Fix issue by matching full instance name while removing old files. Signed-off-by: Rajan Vaja <rajan.vaja@gmail.com> Signed-off-by: Bhargav Patel <br13patel@gmail.com>
* coova-chilli: add uci configuration file, init.d and firewall scriptImre Kaloz2015-04-28