That might not require us to choose a default, however, as long as the kernel can tell libpcap which hash value it's providing (if any). It might, however, mean that we should choose a hash value that, for kernel hashing, is considered "adequate", and recommend that capture mechanisms implement it.
Maybe I missed something, but why does the kernel have to generate the hash? Are we actually worried that the packet data will be corrupted between the kernel and userland?
Also, why is the list setting Reply-to: to <[EMAIL PROTECTED]>, rather than <[EMAIL PROTECTED]>, which is the advertised address of the list?
-- Jefferson Ogata <[EMAIL PROTECTED]> NOAA Computer Incident Response Team (N-CIRT) <[EMAIL PROTECTED]>
- This is the tcpdump-workers list. Visit https://lists.sandelman.ca/ to unsubscribe.
