David Lang wrote:
>the TCP stack already deals with fragments (including duplicates) doesn't
>this process include source/dest ip/port and a sequence number? wouldn't
>this (usually) merge both packets back togeather if they get fragmented on
>the way? if they are small packets this probably won't work, but you would
>not be as worried about duplicating them anyway.
It does, but only at the very end of the link. In between, the duplicates
cross the whole Internet on their way to the target. The target receives
them both and discards whatever comes second.
This will kill performance at the receiving end if the duplicated packets
are large.
If one limits it to small packets <64 bytes, it probably won't affect
the receiving end's bandwidth directly, but it will, indirectly, because
it increases the amount of traffic otherwise flowing in that direction
through the Internet at large (which is why it helps if the duplicates
can be filtered out earlier).
--
Sincerely, [EMAIL PROTECTED]
Stephen R. van den Berg (AKA BuGless).
"Father's Day: Nine months before Mother's Day."
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
