> From: David S. Miller [mailto:davem@redhat.com]
> But I first want to know the real story behind this reboot anomaly.
> Then we will fix any new bug we discover, and apply the icmp patch as
> well.
I've done a bit more testing. The behaviour doesn't change across reboots.
Instead, it seems to be the case that:
If the packet fits within the MTU of the outgoing interface, DF is set.
If the packet doesn't fit, and thus gets fragmented, DF is clear on all
fragments.
Does this make sense?
I think the reason it looked like it changed across reboots might be caused
by the fact that it was influenced by a FreeS/WAN tunnel, which, after a
reboot, didn't always get started successfully.
If the tunnel was down, the packets (2 kB pings) would go out eth0 fragmented
and with DF clear.
If the tunnel was up, they would get routed through the ipsec0 interface
(with a MTU of 16kB) unfragmented and with DF set.
In the latter (normal) case, after arrival and decapsulation at the endpoint
of the tunnel, the packet is doomed because it needs fragmentation to travel
further, but DF is set.
Svenning
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon May 07 2001 - 21:00:24 EST