From: Glenn Terjesen <glenn@webcat.no>
To: netfilter@lists.netfilter.org
Subject: Re: is it possible to block ip packets that contains experimental tcp options ?
Date: Tue, 22 May 2007 10:58:24 +0200 [thread overview]
Message-ID: <1179824305.32083.69.camel@bathory.webcat.no> (raw)
In-Reply-To: <4651E483.9000204@plouf.fr.eu.org>
Thanks allot Pascal,
iptables -A FORWARD -p tcp --tcp-option 76 -j REJECT
seems to be working.
On Mon, 2007-05-21 at 20:27 +0200, Pascal Hambourg wrote:
> Hello,
>
> Glenn Terjesen a écrit :
> > What i meant with "experimental tcp options" is that my ids (snort)
> > keept logging these "experimental tcp options"
> >
> > #
> > code 76
> > length 8
> > data 01019DEDBEF00005
> >
> > I know this aint a snort list, but my servers don't serve any services
> > that require this kind of traffic.
> >
> > So i was wondering if iptables has any way of blocking these.
>
> If you have a black list of options you want to drop (or a white list of
> allowed options), what about the "--tcp-option" option of the "tcp" match ?
>
> > These to magic lines fixed it all
> > iptables -A FORWARD -p tcp --tcp-flags ALL ALL -j DROP
> > iptables -A FORWARD -p tcp --tcp-flags ALL NONE -j DROP
>
> I wonder how these rules could drop packets according to TCP options.
> TCP flag combinations are not TCP options.
>
>
--
Mvh Glenn Terjesen @ Webcat AS
Tlf: +47 37 02 20 20
E-post: support@webcat.no
next prev parent reply other threads:[~2007-05-22 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 17:18 is it possible to block ip packets that contains experimental tcp options ? Marc Cozzi
2007-05-17 17:25 ` is it possible to block ip packets that contains experimentaltcp " Paul Blondé
2007-05-21 11:32 ` is it possible to block ip packets that contains experimental tcp " Glenn Terjesen
2007-05-21 11:55 ` Glenn Terjesen
2007-05-21 18:27 ` Pascal Hambourg
2007-05-22 8:58 ` Glenn Terjesen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-16 12:18 Marc Cozzi
2007-05-16 18:04 ` Jan Engelhardt
2007-05-16 9:23 Glenn Terjesen
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=1179824305.32083.69.camel@bathory.webcat.no \
--to=glenn@webcat.no \
--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