search

LionHear7 / opendpi

Automatically exported from code.google.com/p/opendpi
GNU Lesser General Public License v3.0
0 stars 0 forks source link

Order of operations through wrapper appear to not be parsed correctly #16

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
When using ipp2p with conntrack states, the following syntax works:

iptables -A OUTPUT -p tcp -m ipp2p --winmx -m conntrack --ctstate ESTABLISHED 
-j DROP

This same syntax using the opendpi module does NOT work.  Eg:

iptables -A OUTPUT -p tcp -m opendpi --winmx -m conntrack --ctstate ESTABLISHED 
-j DROP

...gives an error:

xt_opendpi: You need to specify at least one protocol

Switching the order of operators fixes the problem, but this appears to be 
inconsistent with other modules:

iptables -A OUTPUT -p tcp -m opendpi -m conntrack --ctstate ESTABLISHED --winmx 
-j DROP

I'm trying to add support for OpenDPI in Shorewall, and this change of syntax 
is causing issues.

Thanks in advance!

Original issue reported on code.google.com by zebb...@gmail.com on 18 Jul 2011 at 6:08