From: Miguel Angel Amador L <amador@puc.cl>
To: netfilter@lists.netfilter.org
Subject: Re: bad tcp packets
Date: Tue, 23 Nov 2004 09:42:24 -0300 [thread overview]
Message-ID: <1101213743.32475.37.camel@JOKER.INFOWORLD.CL> (raw)
In-Reply-To: <web-23112413@infinito.it>
El mar, 23-11-2004 a las 09:18, hamals@infinito.it escribió:
> Hello to everyone
>
> I'm reading "Iptables Tutorial 1.1.19" by Oskar
> Andreasoon, and I cant understand these bad packets rules
>
>
> $IPTABLES -N bad_tcp_packets
> #
> #
> # bad_tcp_packets chain
> #
> $IPTABLES -A bad_tcp_packets -p tcp --tcp-flags SYN,ACK
> SYN,ACK \
> -m state --state NEW -j REJECT --reject-with tcp-reset
May be that you can't got the three flags on, in the same packet
> $IPTABLES -A bad_tcp_packets -p tcp ! --syn -m state
> --state NEW -j LOG \
> --log-prefix "New not syn:"
> $IPTABLES -A bad_tcp_packets -p tcp ! --syn -m state
> --state NEW -j DROP
May be, if the packet haven't the syn flags on, the packet is not new
> someone could explain me why that are bad tcp packets?
I don't secure, but i thing that is this.
regards
Miguel Amador
> Thanks
>
> _______________________________________
> Connessione ed e-mail gratuita da 10 mb
> consultabile tramite web e tramite pop.
> www.infinito.it vieni a scoprire tutti
> i nostri servizi!
>
> http://www.infinito.it/xmail
>
>
next prev parent reply other threads:[~2004-11-23 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 12:18 bad tcp packets hamals
2004-11-23 12:42 ` Miguel Angel Amador L [this message]
2004-11-23 13:49 ` Jason Opperisano
2004-11-23 13:59 ` Frank Gruellich
-- strict thread matches above, loose matches on Subject: below --
2004-11-23 13:39 Scott Knake
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=1101213743.32475.37.camel@JOKER.INFOWORLD.CL \
--to=amador@puc.cl \
--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