> Also, I do not see much difference between the first statement above and the > last, which executes in the net2fw chain, which in turn, is part of INPUT. In > other words, I have this: > > -A INPUT -p udp --dport 67:68 -i eth0 -j ACCEPT > -A INPUT -i eth0 -j net2fw > [...] > -A net2fw -m conntrack --ctstate NEW,INVALID -j ~blacklist0 -m comment > --comment "BLACKLIST" > -A net2fw -i eth0 -j eth0_iop > [...] > -A eth0_iop -m conntrack --ctstate NEW,INVALID -j smurfs > -A eth0_iop -p udp --dport 67:68 -j ACCEPT > > The last statement above is exactly the same as the first! Since upgrading to 4.5.8-Beta1, I am unable to reproduce this (with the same shorewall configuration), so I presume whatever it was that was causing this, it has now been fixed.
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
