Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
GoogleCodeExporter opened this issue Apr 27, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

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 [email protected] on 18 Jul 2011 at 6:08

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant