No problem.
IPCamsBlock.sh does allow the ability to
influence the
NTP access, but I deliberated about adding similar functionality to
IoTBlock.sh as
NTP access rules are probably
global rather than for each individual IoT group/chain?
So currently, using the
'IoT_Wemo.apps' file won't work as the chain name wouldn't match, as the
NTP rule(s) wouldn't be visible in your WeMo device chain so I wouldn't be able to associate a global
NTP redirect rule with a specific IoT chain when you specified the
'report' or
'del' options.
At the moment I'm not able to access/create/test
v1.02b of my script to accommodate your requirement but it should be pretty simple e.g. add something like
'localntp="xxx.xxx.xxx.xxx" as a command line option, however in the interim, you would probably need to manually use something like this:
Code:
iptables -t nat -I PREROUTING -i br0 -s 192.168.xxx.140/31 -p udp --dport 123 -j DNAT --to-destination $(nvram get lan_ipaddr) -m --comment "Wemo"
or (if you are on a back-level firmware)
iptables -t nat -I PREROUTING -i br0 -s 192.168.xxx.140/31 -p udp --dport 123 -j DNAT --to-destination $(nvram get lan_ipaddr)
