fixes#698
As advised in UDA:
Due to the unreliable nature of UDP, devices SHOULD send the entire set
of discovery messages more than once with some delay between sets e.g. a
few hundred milliseconds. To avoid network congestion discovery messages
SHOULD NOT be sent more than three times. In addition, the device MUST
re-send its advertisements periodically prior to expiration of the duration
specified in the CACHE-CONTROL header field; it is RECOMMENDED that such
refreshing of advertisements be done at a randomly-distributed interval
of less than one-half of the advertisement expiration time.
(CACHE-CONTROL value is minimum 1800 seconds, so the interval should be
less than 900s
NFtables uses the INET table for NAT which combines IPv4 and IPv6.
Older systems might not have this option and use the ip table instead.
This adds a flag to fall back to the ip table style.
Signed-Off-By: Sven Auhagen <sven.auhagen@voleatech.de>
Some reports that a certain app is abusing UPnP for exploiting upload
bandwidth. This commit adds support to restrict UPnP rules to a regex.
By matching requester's description string against rule's regex, this
will make some obstacles for that app.
To hardcode table and chain creation and deletion makes it impossible
for existing firewall infrastructures to integrate miniupnpd.
NFTables will either reevaluate packets through miniupnpd or
it will delete existing tables when there are already custom chains in it.
Signed-off-by: Sven Auhagen <sven.auhagen@voleatech.de>
you now can setup :
listening_ip=igb1 bridge0 xxx0 xxx1 ...
miniupnpd will use igd1 address, but will not complain when receiving
packets from either igb1, bridge0, xxx0 or xxx1
fixes#379
see also #408
- manufacturer_name, default is "`uname -s`"
- manufacturer_url, default is URL of OS verndor
- model_name, default is "`uname -s` router"
- model_description, default is "`uname -s` router"
- model_url, default is URL of OS verndor