From: Willy Tarreau <w@1wt.eu>
To: Krzysztof Oledzki <ole@ans.pl>
Cc: haproxy@formilux.org, netdev@vger.kernel.org
Subject: Re: ISNs and 2.6.22, Was: Re: haproxy & linux firewall (netfilter)
Date: Sat, 20 Oct 2007 23:52:01 +0200 [thread overview]
Message-ID: <20071020215201.GA12894@1wt.eu> (raw)
In-Reply-To: <Pine.LNX.4.64.0710201921000.19637@bizon.gios.gov.pl>
On Sat, Oct 20, 2007 at 07:23:25PM +0200, Krzysztof Oledzki wrote:
(...)
> >So it seems that ISNs are not randomly incremented but rather randomly
> >generated. Adding netdev@vger.kernel.org to the CC list.
>
> Eh, I was little to hurry this time. There were not randomly generated but
> incremented with to big value. This patch fixes my problem:
>
> http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git;a=blob;f=queue-2.6.22/fix-tcp-initial-sequence-number-selection.patch;h=05b9167d68ecde1e6088f58c55e2906b768420ed;hb=HEAD
Good catch Krzysztof ! I've already noticed that one on LKML but did not
make the connection with your problem!
Please also tell Jozsef so that if he gets other reports, he knows where
to point the reporters.
Regards,
Willy
prev parent reply other threads:[~2007-10-21 1:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0710192358340.17074@bizon.gios.gov.pl>
[not found] ` <20071020055604.GA1371@1wt.eu>
[not found] ` <Pine.LNX.4.64.0710201422220.17074@bizon.gios.gov.pl>
[not found] ` <20071020133101.GB3490@1wt.eu>
[not found] ` <Pine.LNX.4.64.0710201544290.17074@bizon.gios.gov.pl>
[not found] ` <20071020150035.GA12878@1wt.eu>
2007-10-20 17:08 ` ISNs and 2.6.22, Was: Re: haproxy & linux firewall (netfilter) Krzysztof Oledzki
2007-10-20 17:23 ` Krzysztof Oledzki
2007-10-20 21:52 ` Willy Tarreau [this message]
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=20071020215201.GA12894@1wt.eu \
--to=w@1wt.eu \
--cc=haproxy@formilux.org \
--cc=netdev@vger.kernel.org \
--cc=ole@ans.pl \
/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).