Date: Tue, 12 Dec 2006 19:01:27 -0600
From: Christy L Norman <cnorman@us.ibm.com>
Subject: [users:00273] mobility CN tests: failing checksum
To: users@tahi.org
Message-Id: <OFE0E1CC11.923256A1-ON86257243.00024A56-86257243.0005A0DE@us.ibm.com>
X-Mail-Count: 00273

Tahi users,

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, "The Next 
Header value used in the pseudo-header is 2.")  It 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?

Thanks,

Christy
	
273_2.html (attatchment)(tag is disabled)