From: Rick Jones <rick.jones2@hp.com>
To: Mark Lord <lkml@rtr.ca>
Cc: David Miller <davem@davemloft.net>,
jheffner@psc.edu, torvalds@osdl.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.17: networking bug??
Date: Tue, 13 Jun 2006 15:12:31 -0700 [thread overview]
Message-ID: <448F384F.8050207@hp.com> (raw)
In-Reply-To: <448F32E1.8080002@rtr.ca>
Mark
From everything I have read so far (which admittedly hasn't been
everything) it sounds like the firewall in question was a ticking
timebomb. If 2.6.17 hadn't set it off, something else might very well
have done so.
Or, if you prefer another metaphore, 2.6.17 was simply the last in a
series of straws on the back of the camel what was the firewall. Meta
issues of whether or not the camel that is firewalls should have ever
been allowed to poke its nose in the Internet Tent notwithstanding :)
At the very least, the firewall, if it is going to be "stateless," has
to strip the window scaling option from the SYN's that go past.
Otherwise, I would be inclined to agree with David that the firewall is
fundamentally broken.
rick jones
next prev parent reply other threads:[~2006-06-13 22:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <448EC6F3.3060002@rtr.ca>
[not found] ` <448ECB09.3010308@rtr.ca>
2006-06-13 15:00 ` 2.6.17: networking bug?? Mark Lord
2006-06-13 15:28 ` Mark Lord
2006-06-13 16:58 ` Mark Lord
2006-06-13 17:22 ` Mark Lord
2006-06-13 17:39 ` John Heffner
2006-06-13 17:50 ` Linus Torvalds
2006-06-13 18:26 ` Mark Lord
2006-06-13 19:08 ` Mark Lord
2006-06-13 21:26 ` David Miller
2006-06-13 21:49 ` Mark Lord
2006-06-13 22:12 ` Rick Jones [this message]
2006-06-13 22:23 ` David Miller
2006-06-13 22:40 ` Rick Jones
2006-06-13 23:01 ` David Miller
2006-06-14 1:25 ` John Heffner
2006-06-13 23:22 ` Matt Mackall
2006-06-19 7:07 ` Helge Hafting
2006-06-14 5:18 ` Andi Kleen
2006-06-14 8:09 ` Daniel Drake
2006-06-13 18:28 ` John Heffner
2006-06-13 20:45 ` Barry K. Nathan
2006-06-13 22:09 ` Chase Venters
2006-06-13 22:23 ` David Miller
2006-07-02 17:39 ` Jan Knutar
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=448F384F.8050207@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=jheffner@psc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=netdev@vger.kernel.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).