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>
Instead of passing a wildcard source to the expected RTP data connection;
use the server IP address of the RTSP SETUP packet or the RTP media source
from the SETUP URI contained in the SETUP packet.
This guarantees RTP data is only accepted from the expected source.
Signed-off-by: Alin Nastac <alin.nastac@gmail.com>
Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
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>
Removed libtalloc dependency and adjusted configure args to skip some tests. Those packages were not being built anyway.
Size difference: 14405 vs. 14125 on mvebu. Also 11275 bytes for libtalloc are gone.
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>
Two issues:
1. The fwknopd init script did not handle unprepared logical networks.
This is fixed by A) not defining instance for procd when the physical
interface is unknown, and B) by watching the logical network for
changes.
2. When using PPPoE, there are two physical interfaces -- one for raw
PPPoE communication and one for wrapped communication. The function
network_get_physdev returns the physical device, while the function
network_get_device returns the wrapped one -- we shall use the
wrapped interface. Usually (for non-wrapped interfaces) the physdev
and device are the same, also other network scripts use the latter
function.
Both issues found by and thanks are going to @lucize.
Signed-off-by: Oldřich Jedlička <oldium.pro@gmail.com>
Sometimes it's necessary to set per-host options like:
list dhcp_option 'option:always-broadcast,true'
for hosts that don't understand unicast replies. There might
be other options you might want to set on a per-host basis,
such as extensions-path, dhcp-message-text, etc.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
Some /etc/config-destined files are in files/ and suffixed with
.conf while others are in files/etc/config/ which isn't consistent.
Put everything in files/ and call it good.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
Christian Lachner