From: Fabbione <fabio.m.d.nitto@ted.ericsson.dk>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Possibly OT] ipt_unclean.c on kernel-2.4.7-9
Date: Tue, 28 Aug 2001 12:49:08 +0200 [thread overview]
Message-ID: <3B8B7724.EEC95BDD@ted.ericsson.dk> (raw)
In-Reply-To: <E15bW2B-0001Ur-00@localhost>
Well probably the documentation should be more explicit. I know that's
experimental
code but someone has to use it in order to increase its quality.
My idea of building the rules was to DROP as much as possible all the
"dirty"
packets before the packets can match the rules that allow connections.
Regarding ECN I've it on on most of my boxes without any problems (I
don't care
if I cannot look to lego.com). but I don't want to restart again the ECN
discussion
there were sometimes ago in the ML.
Cheers
Fabio
Rusty Russell wrote:
>
> In message <3B8A262C.82ED7793@ted.ericsson.dk> you write:
> > Hi gurus,
> > I've possibly found a bug in the iptables unclean match support
> > but I was not able to find the email of the mantainer so I'm posting
> > here....
> >
> > the module is incorrectly matching ftp session. Ex:
> >
> > iptables -j DROP -A INPUT --match unclean
> > iptables -j ACCEPT -A INPUT -p tcp --dport 21
> >
> > in this case all my packets directed to the ftp server where dropped by
> > the
> > "unclean" match and this make impossible to open ftp session.
>
> Please do not do this. "unclean" should be renamed "interesting": you
> should log these packets, but probably not drop them, otherwise some
> things may break.
>
> Like ECN...
>
> Cheers,
> Rusty.
> --
> Premature optmztion is rt of all evl. --DK
prev parent reply other threads:[~2001-08-28 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 10:51 [Possibly OT] ipt_unclean.c on kernel-2.4.7-9 Fabbione
2001-08-27 23:43 ` Rusty Russell
2001-08-28 10:49 ` Fabbione [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=3B8B7724.EEC95BDD@ted.ericsson.dk \
--to=fabio.m.d.nitto@ted.ericsson.dk \
--cc=fabbione@fabbione.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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