From: Patrick McHardy <kaber@trash.net>
To: Martijn Posthuma <posthuma@sangine.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: SYN,URG combination considered INVALID by tcp conntrack
Date: Tue, 13 Feb 2007 12:22:31 +0100 [thread overview]
Message-ID: <45D19F77.609@trash.net> (raw)
In-Reply-To: <20060905144620.a7937f80.posthuma@sangine.com>
Martijn Posthuma wrote:
> We have been experiencing problems with tcp connection establishment when (for some reason) the URG flag and pointer were set in the SYN segment. The problem did not affect all machines that were contacted but a subset. All affected machines were using netfilter-conntrack and firewalling.
> Inspection of the conntrack code (on a 2.6 linux kernel source) reveiled that the above mentioned combination of flags is not considered valid. The code I am referring to is in nf_conntrack_proto_tcp.c version 2.2, lines 768 to 795:
>
> [..]
>
> As you can see the SYN,URG combination is not considered valid. I can not find any justification for this in RFC793. I do realize that it is a rare combination of flags, but legal none the less. (In the RFC there is even a explicit mention of the fact that a SYN segment can contain data, so a URG flag is perfectly feasible in that case).
>
> Does someone know of a good reason that this flag combination is excluded?
No reason, I've added SYN|URG and SYN|PUSH|URG to the valid flag
combinations, thanks.
next prev parent reply other threads:[~2007-02-13 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 12:46 SYN,URG combination considered INVALID by tcp conntrack Martijn Posthuma
2007-02-13 11:22 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-06 12:47 Martijn Posthuma
2006-09-06 18:20 ` Patrick McHardy
2006-09-07 7:08 ` Martijn Posthuma
2006-09-07 15:01 ` Patrick McHardy
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=45D19F77.609@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=posthuma@sangine.com \
/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;
as well as URLs for NNTP newsgroup(s).