Very Senior Member
There are inherent ASUS implemented firewall rules that refer to '-j logdrop'
so presumably in the SECURITY chain (and if the USER enables Network Services Filter) etc. then ASUS deems it a requirement to write a tracking message to Syslog rather than silently DROP the packet.Code:
iptables-save | grep -E "logdrop" :logdrop - [0:0] -A INPUT -i eth0 -p icmp -m icmp --icmp-type 8 -j logdrop -A INPUT -m state --state INVALID -j logdrop -A INPUT -j logdrop -A FORWARD -m state --state INVALID -j logdrop -A NSFW -i br0 -o eth0 -j logdrop -A SECURITY -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -j logdrop -A SECURITY -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK RST -j logdrop -A SECURITY -p icmp -m icmp --icmp-type 8 -j logdrop -A logdrop -j DROP -A other2wan -j logdrop
When Skynet is installed, this expected logging functionality is no longer available - no idea why Skynet now wishes to interfere and unilaterally prevent firewall rule trigger messages being written to Syslog?
(NOTE: Even if you temporarily disable Skynet, it doesn't restore the logdrop chain.)
P.S. You can provide the 'fixskynet' directive when requesting IPCamsBlock.sh and both the script and the ASUS firewall rules will work as intended.
Thank you much appreciated