From: Lopsch <lopsch@lopsch.com>
To: Netfilter-Mailinglist <netfilter@lists.netfilter.org>
Subject: Re: question about --tcp-flags
Date: Fri, 03 Dec 2004 00:44:00 +0100 [thread overview]
Message-ID: <41AFA8C0.4010006@lopsch.com> (raw)
In-Reply-To: <1102028933.3217.2.camel@hubcap.ljm.dom>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
Jason Opperisano schrieb:
> On Thu, 2004-12-02 at 17:34, Lopsch wrote:
>
>>Thank´s will take look at that list :). But a last question. --syn is
>>the same as --tcp-flags ALL SYN?
>
>
> no. "--syn" is the example you asked about:
>
> --tcp-flags SYN,RST,ACK SYN
>
> this is clearly explained in 'man iptables' btw...
>
> -j
>
> --
> "Fame was like a drug. But what was even more like a drug were
> the drugs."
> --The Simpsons
Yes I know but the manpages don´t work here don´t know why. Hmm but then
it´s better to explicit drop packets like ... --tcp-flags SYN,FIN
SYN,FIN before using a line like this ... --syn -m state --state NEW ...
because this would also allow the usage of SYN,FIN for new connections.
And that´s not a legal set. Or isn´t it necessary to drop those packets
because TCP will take care of that and send RST for them?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 825 bytes --]
next prev parent reply other threads:[~2004-12-02 23:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 22:08 question about --tcp-flags Lopsch
2004-12-02 23:11 ` Jason Opperisano
2004-12-02 22:34 ` Lopsch
2004-12-02 23:08 ` Jason Opperisano
2004-12-02 23:44 ` Lopsch [this message]
2004-12-02 23:57 ` Jason Opperisano
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=41AFA8C0.4010006@lopsch.com \
--to=lopsch@lopsch.com \
--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