From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Gáspár Lajos" <swifty@freemail.hu>
Cc: Rob Sterenborg <rob@sterenborg.info>, netfilter@lists.netfilter.org
Subject: Re: STRING module : Invalid argument
Date: Thu, 05 Oct 2006 12:34:10 +0200 [thread overview]
Message-ID: <4524DFA2.9030504@netfilter.org> (raw)
In-Reply-To: <45239360.6060304@freemail.hu>
Gáspár Lajos wrote:
> Rob Sterenborg írta:
>> On Wed, October 4, 2006 10:03, G�sp�r Lajos wrote:
>>
>>> Hi,
>>>
>>> fw1:~# iptables -v -A INPUT -j DROP -p tcp -m string --string "test"
>>> DROP tcp opt -- in * out * 0.0.0.0/0 -> 0.0.0.0/0 STRING match
>>> "test"
>>> iptables: Invalid argument
>>>
>>>
> Does it means that it fails at insertation of the rule into the chain,
> doesn't?
Yes
>> - You probably don't have the string module installed and/or loaded.
>> - Kernel 2.6.18 is rather new (sep-2006) and iptables 1.2.11 is rather
>> old
>> (june 2004). Upgrade to a new iptables version: 1.3.6 is just released.
>>
>>
> I have already tried it with the Debian backport of iptables (v1.3.x)
> ... Same results.
Debian backport of iptables? What do mean?
> Right now I am recompiling the kernel and iptables + pom-ng.
> Hope it helps... :)
The string match was introduced in kernel 2.6.16 if my mind serves well,
the old version that was available in pom-ng was broken. You also need a
recent iptables version to make it work as Rob pointed out.
--
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris
prev parent reply other threads:[~2006-10-05 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 8:03 STRING module : Invalid argument Gáspár Lajos
2006-10-04 9:45 ` Rob Sterenborg
2006-10-04 10:56 ` Gáspár Lajos
2006-10-05 10:34 ` Pablo Neira Ayuso [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4524DFA2.9030504@netfilter.org \
--to=pablo@netfilter.org \
--cc=netfilter@lists.netfilter.org \
--cc=rob@sterenborg.info \
--cc=swifty@freemail.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox