I just needed to educate myself a bit more
....you have IP Traffic monitoring active and changed the Logged packets types settings which lead to some entries I hadn't see before.
For a test, can you change the Logged packets types back to 'None' (I think this will bring back the entry I was looking for), and then try the iptables command again?
Haha
I disabled the IP Traffic monitoring and did the command again without luck.
admin@RT-N66U:/tmp/home/root# iptables -D FORWARD -m state --state INVALID -j DROP
iptables: Bad rule (does a matching rule exist in that chain?)
This is the chain:
Chain FORWARD (policy DROP)
target prot opt source destination
logaccept all -- anywhere anywhere state RELATED,ESTAB LISHED
logdrop all -- anywhere anywhere
logdrop all -- anywhere anywhere state INVALID
ACCEPT all -- anywhere anywhere
logaccept all -- anywhere anywhere
DROP icmp -- anywhere anywhere
logaccept tcp -- anywhere anywhere tcp flags:FIN,SYN,R ST,ACK/SYN limit: avg 1/sec burst 5
logaccept tcp -- anywhere anywhere tcp flags:FIN,SYN,R ST,ACK/RST limit: avg 1/sec burst 5
logaccept icmp -- anywhere anywhere icmp echo-request l imit: avg 1/sec burst 5
logaccept all -- anywhere anywhere ctstate DNAT
ACCEPT all -- anywhere anywhere