<br><font size=2 face="sans-serif">Tahi users,</font>
<br>
<br><font size=2 face="sans-serif">I'm running the mobility suite against
a machine in our lab and all the tests are failing because of an inbound
checksum problem. The system receiving the packets is calcuating the checksum
using the mobility pseudo-header with the next header value of 2. (RFC
3755 says,</font><font size=2 face="Arial"> "The Next Header value
used in the pseudo-header is 2.") It </font><font size=2 face="sans-serif">seems
that the Tahi packets are built calculating the pseudo header with a next
header value of 135. Has anyone else seen a difference in checksums?</font>
<br>
<br><font size=2 face="sans-serif">Thanks,</font>
<br>
<br><font size=2 face="sans-serif">Christy</font>