VanLUG Email Archive
> On Mon, 31 Aug 1998, Kaz Kylheku wrote:
>
> > I have a very reliable and knowledgeble friend who has apparently determined
> > that NT (now I don't know what version!) sets the ``do not fragment'' bit on
> > outgoing datagrams.
>
> That would be normal for a machine that does path MTU discovery.
That's what I was thinking too; I won't know until I've done more investigation
myself. I had intended to edit the above message more, but I sent it
accidentally! :)
You would expect that once the path MTU discovery is satisified, packets
without don't-fragment bits would start coming in, of course. However, the
person who reported his finding to me was not able to get any communication
going with the machine in question at all until he raised the MTU on his PPP
interface.
> > Presumably, NT can't deal with incoming
> > fragmented packets either...
>
> As far as I know, it does deal just fine with fragmented packets.
Hmm. Yeah, it *would* be a gaping incompliance. (Then again, they didn't handle
out of band data properly either, so it wouldn't be surprising! :)
> > > Time moves on, so should any OS... If it's to anquard to maintain backward
> > > compability, don't... Progress...
>
> Uh, you're talking not just about not maintaining backward
> compatability with Linux, but not maintaining backward compatability
> with hundreds of millions of devices around the world, and not
> conforming to the IPv4 standards. You may feel you can just chuck
I think you mixed up the quotes here, but then this is because I left too much
of the original quoted message hanging at the end of my reply due to the
aforementioned accidental send. Apologies.