>> :Can you guys elaborate on the problem? Was it on incoming checksums, >> :outgoing checksums, or both? >> >> It was on incoming checksums I believe. > >Was the result a rejected packet that didn't get transferred, or >transferred packets with bad checksums? > >If the latter, then it's workaroundable in software, which might >be worth doing... if only rechecking packets with bad checksums. >I fear the former makes more sense, though. 8-(.
The chip would calculate the wrong checksum and basically say the packet was bad when it was good (and by inference, good when it was bad). I was not able to figure out what they got wrong in the algorithm, but if that were known, then it is conceivable that the problem could be fixed in software. -DG David Greenman-Lawrence Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com President, Download Technologies, Inc. - http://www.downloadtech.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
