From: Rick Jones <rick.jones2@hp.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>,
Paul P Komkoff Jr <i@stingr.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Was change to ip_push_pending_frames intended to break udp (more specifically, WCCP?)
Date: Mon, 22 May 2006 14:06:28 -0700 [thread overview]
Message-ID: <447227D4.4050407@hp.com> (raw)
In-Reply-To: <1148332293.17376.114.camel@localhost.localdomain>
Alan Cox wrote:
> On Llu, 2006-05-22 at 11:48 -0700, Rick Jones wrote:
>
>>ID of zero again? I thought that went away years ago? Anyway, given
>>the number of "helpful" devices out there willing to clear the DF bit,
>>fragment and forward, perhaps always setting the IP ID to 0, even if DF
>>is set, isn't such a good idea?
>
>
> Any device that clears DF is so terminally broken that you've already
> lost the battle the moment you bought it.
Perhaps, but still, always setting the IP datagram ID to the same value
even with the DF bit set seems contrary to the "conservative in what we
send" that is so often brought-forth as a reason a stack behaves the way
it does.
rick jones
next prev parent reply other threads:[~2006-05-22 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060520191153.GV3776@stingr.net>
2006-05-20 21:04 ` Was change to ip_push_pending_frames intended to break udp (more specifically, WCCP?) Andrew Morton
2006-05-22 18:22 ` Vlad Yasevich
2006-05-22 18:48 ` Rick Jones
2006-05-22 18:54 ` Vlad Yasevich
2006-05-22 20:21 ` Paul P Komkoff Jr
2006-05-22 21:10 ` Vlad Yasevich
2006-05-22 21:11 ` Alan Cox
2006-05-22 21:06 ` Rick Jones [this message]
[not found] ` <20060522.161951.92584947.davem@davemloft.net>
2006-05-23 8:13 ` Paul P Komkoff Jr
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=447227D4.4050407@hp.com \
--to=rick.jones2@hp.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=i@stingr.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vladislav.yasevich@hp.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).