> 1) TCP connection exists
> 2) arp cache changes
> 3) arp cache is correct
> 4) TCP packets for that existing connection are still sent to the old Ethernet address
I'm not surprised that the problem exists. 2.0 previously had problems with
route changes on TCP retransmits, there are probably other horrors lurking
too. The problem is that in 2.0 the retransmit queue is managed by the link
layer, which causes all kinds of problems. In 2.1/2.2 all this was solved
bya rewrite - TCP packets in the retransmit queue are headerless now
so this should never occur. It is probably possible to fix it in 2.0 (by
calling dev->rebuild_header at the right time), but the fix will be ugly.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/