2006/11/15, Wojciech Ziniewicz <wojciech.ziniewicz@gmail.com>:
2006/11/15, Nate Duehr <nate@natetech.com>: > > After a while, it becomes more intuitive, if you haven't been doing it > for a long time. Your brain and your instincts remind you that someone > made a change on X date, and that change is probably the reason for the > "other" problems you're seeing in unexpected places. >
Today I saw dmesg (I wasnt looking into it for a long time ) ------------ UDP: bad checksum. From 81.100.129.129:18393 to 217.17.38.250:25840 ulen 280 UDP: bad checksum. From 80.207.215.58:4672 to 217.17.38.185:35220 ulen 35 UDP: bad checksum. From 80.207.215.58:4672 to 217.17.38.185:35220 ulen 35 UDP: bad checksum. From 81.103.209.33:31515 to 217.17.38.250:25840 ulen 286 UDP: bad checksum. From 86.6.232.110:41700 to 217.17.38.113:27883 ulen 282 UDP: bad checksum. From 58.23.99.44:27364 to 217.17.38.231:21035 ulen 310 UDP: bad checksum. From 86.6.238.145:20436 to 217.17.38.231:21035 ulen 310 ----------- There are many of theese in dmesg ... this bad checksums are generated by p2p software (looking on the ports) but i'm not shure if it is a hardware problem or the bad soft that is not respecting isos/rfc's/other norms... -- Wojciech Ziniewicz | jid:zeth@chrome.pl http://silenceproject.org | http://zetho.wordpress.com