Linux Netfilter discussions
 help / color / mirror / Atom feed
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: Mon, 21 May 2007 13:32:14 +0200	[thread overview]
Message-ID: <1179747134.32083.19.camel@bathory.webcat.no> (raw)
In-Reply-To: <F163413C9250D211A55C0060979D5280016AB361@hertz.rad.nd.edu>

Hi,
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.

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


Thanks alot for the help.


On Thu, 2007-05-17 at 13:18 -0400, Marc Cozzi wrote:
>  Paul,
> 
> I believe that's correct. Although I'm still not
> Sure what was originally meant by "experimental tcp options".
> 
>   -marc
> 
> > -----Original Message-----
> > From: Paul Blondé [mailto:jpb@entel.ca] 
> > Sent: Thursday, May 17, 2007 11:09 AM
> > To: netfilter@lists.netfilter.org
> > Subject: RE: is it possible to block ip packets that contains 
> > experimentaltcp options ?
> > 
> > I assume that LOG-AND-DROP is your own chain, crafted so that 
> > you can perform both functions with a single entry?
> > 
> > 
> > 
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > Paul Blondé
> >  
> > 
> > 
> > > -----Original Message-----
> > > From: netfilter-bounces@lists.netfilter.org
> > > [mailto:netfilter-bounces@lists.netfilter.org] On Behalf Of 
> > Marc Cozzi
> > > Sent: Wednesday, May 16, 2007 5:19 AM
> > > To: netfilter@lists.netfilter.org
> > > Subject: RE: is it possible to block ip packets that contains 
> > > experimentaltcp options ?
> > > 
> > > 
> > > 
> > > Glenn,
> > > 
> > > Not sure what you mean by "experimental" however, there are some 
> > > conditions of flags that should never occur on the network. 
> > These can 
> > > be trapped with rules similar to the following.
> > > 
> > > iptables -A BLOCKED -m state --state INVALID -j 
> > LOG-AND-DROP iptables 
> > > -A BLOCKED -p tcp --tcp-flags ALL ALL -j LOG-AND-DROP iptables -A 
> > > BLOCKED -p tcp --tcp-flags ALL NONE -j LOG-AND-DROP
> > > 
> > >   --marc
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: Glenn Terjesen [mailto:glenn@webcat.no]
> > > > Sent: Wednesday, May 16, 2007 5:24 AM
> > > > To: netfilter@lists.netfilter.org
> > > > Subject: is it possible to block ip packets that contains 
> > > > experimental tcp options ?
> > > > 
> > > > Hello,
> > > > got a iptables firewall filtering our servers.
> > > > 
> > > > Is it possible to block tcp packets that contains 
> > experimental tcp 
> > > > options ?
> > > > 
> > > > AND is it smart to do so ?
> > > > 
> > > > 
> > > > --
> > > > Mvh Glenn Terjesen @ Webcat AS
> > > > Tlf: +47 37 02 20 20
> > > > E-post: support@webcat.no
> > > > 
> > > 
> > 
> > 
> 
> 
-- 
Mvh Glenn Terjesen @ Webcat AS
Tlf: +47 37 02 20 20
E-post: support@webcat.no


  parent reply	other threads:[~2007-05-21 11:32 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 ` Glenn Terjesen [this message]
2007-05-21 11:55   ` is it possible to block ip packets that contains experimental tcp " Glenn Terjesen
2007-05-21 18:27   ` Pascal Hambourg
2007-05-22  8:58     ` Glenn Terjesen
  -- 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=1179747134.32083.19.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