From: Shawn <core@enodev.com>
To: juanca <juanca@sat.com.py>
Cc: "netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Subject: Re: kazaa rulset
Date: 28 Jul 2003 16:51:04 -0500 [thread overview]
Message-ID: <1059429064.6146.11.camel@localhost> (raw)
In-Reply-To: <3F2598BD.6050302@sat.com.py>
Having some trouble?
On Mon, 2003-07-28 at 16:42, juanca wrote:
> iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -p tcp -m state --state NEW -m string --string
> "Kazaa" -j DROP
>
> this is my rulset but get this message when run the script what`s wrong?
> iptables: No chain/target/match by that name
> iptables: No chain/target/match by that name
> Bad argument `tcp'
> Try `iptables -h' or 'iptables --help' for more information.
> Bad argument `udp'
> Try `iptables -h' or 'iptables --help' for more information.
> iptables: No chain/target/match by that name
> iptables: No chain/target/match by that name
> iptables: No chain/target/match by that name
> iptables: No chain/target/match by that name
> iptables: No chain/target/match by that name
> iptables v1.2.6a: Couldn't load match
> `--string':/lib/iptables/libipt_--string.so: cannot open shared object
> file: No such file or directory
>
> Try `iptables -h' or 'iptables --help' for more information.
> iptables: No chain/target/match by that name
next prev parent reply other threads:[~2003-07-28 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 21:42 kazaa rulset juanca
2003-07-28 21:51 ` Shawn [this message]
2003-07-29 0:40 ` state --string Ralf Braga
2003-07-29 9:22 ` Maciej Soltysiak
-- strict thread matches above, loose matches on Subject: below --
2003-07-28 21:51 kazaa rulset George Vieira
2003-07-29 1:16 Bill Chappell
2003-07-29 1:17 Bill Chappell
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=1059429064.6146.11.camel@localhost \
--to=core@enodev.com \
--cc=juanca@sat.com.py \
--cc=netfilter@lists.netfilter.org \
/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