Re: [PATCH] --bad CRC

[Ed3f <ed3f () antifork org>]

> Are you aware of this and have you tried --bad from machine with such
> hardware and checked the packets on the other side?

The kernel has control over it. However this is generally used only for the 
checksum at IP level.

Curiosity: TCP checksum of a source route packets is invalid while it's
in flight, because it is based on the final destination IP address, which is
altered as the source route is followed (at the destination, it will be
correct).

In the end, I think this is not a problem, but I'd be very happy to get 
feedback from people running that hardware (generally gigabit cards).

Let me know.



_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev