Rewritten Pull for #5885
When ran from the command line, the script prints
error messages like below. They are caused by supplying
empty "$password" and "$URL_PASS" for some log messages
like "130822 : Detect local IP on 'interface'".
The fix is to check if the values are not empty before running
through sed.
/etc/init.d/ddns start
sed: no previous regexp
Reported by Marc Benoit <marcb62185@gmail.com>
Signed-off-by: Christian Schoenebeck <christian.schoenebeck@gmail.com>
Package configure script decided to use libidn2 already now that it
became available. This triggered a dependency error:
Package libgnurl is missing dependencies for the following libraries:
libidn2.so.0
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
This commit adds a simple procd init script for bcp38 with the sole purpose
to register a configuration change trigger for /etc/config/bcp38.
The change will allow for automatic firewall reloads triggered by invoking
/sbin/reload_config or through ubus config change events emitted by LuCI.
With the init script in place and started, calling
ubus call service event '{"type":"config.change","data":{"package":"bcp38"}}'
or
/sbin/reload_config
will issue an /etc/init.d/firewall reload if /etc/config/bcp38 has been
modified since the last reload_config call.
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
As acme.sh has releases, switch to using those. Update the version accordingly.
Also rearranged some stuff in the hope that uscan will start tracking releases instead of git commits. Makefile is more simple as a result.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
To fix the shell local issue in the ubus mwan3 rpcd shell script, move
the switch case statment into a function.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
dhcrelay has the ability to monitor interfaces for requests
in a single direction only rather than listening to all
interfaces for requests.
Doing this allows one to suppress the duplication of having
the relay forward requests from the same network that the
DHCP server is on.
Signed-off-by: Brian J. Murrell <brian@interlinx.bc.ca>
In a tool like this one, you really want an option to establish if the service
should start or not by default on boot time, especially when its configuration
file has to be customized by the user.
In the configuration file, the new 'enabled' option is setted to '0' by default
since the configuration provided by default will not be the one finally used.
In the init script, the new 'enabled' option is setted to '1' by default in
order to support the previous configuration file behaviour.
Signed-off-by: Adrià Llaudet <adria.llaudet@gmail.com>
W. Michael Petullo