>> > I've just get this 'UDP: bad checksum' messaga again :
>> >
>> > Dec 3 18:36:16 oxygene kernel: UDP: bad checksum. From 193.6.41.136:138 to 193.6.41.255:138 ulen 228
>> >
>> > It's strange that I get this message when somebody boot Windows98 on
>> > 193.6.41.136. Nice :)
>>
>> I think that this is from a BOOTP or DHCP request. Should these
>> kinds of messages still be printing out?
No. This is from Windows Filesharing. (look in /etc/services).
>
>More to the point, why is the kernel evaluating these as bad checksums?
>Is there anyway to recognize these sorts of messages beforehand, so the
>kernel knows the checksum is invalid/special. I'm not all the familiar
>with the protocols in question, but it seems to me that this is really an
>erroneous error message (from the department of redundancy department).
No. Actually, based on other messages recently going to the list about bad
checksums, the reason the kernel is printing the message is because it
really does have a bad checksum :-). What a suprise :-)
Mike Sackton
-- "I always try to make sure that I never spell the word typo wrong, because I think that would look really silly." -- Laura Sackton
- 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/