On 8/3/07, lily zhao <Lily.Zhao at sun.com> wrote:> Dear All,
> we met some problem with UDP checksum, and hope to use dtrace to find
> the reason and resolve it, now I have using following dtrace script:
>
> dtrace -n ''ip_cksum:return /arg1!=65535/ {printf("%d\n",
arg1");}''
>
> which show that the ip checksum is not corrent, sometime the packet
checksum is not 0xffff. I want to use dtrace to detect why the checksum is not
orrect,
> does the checksum received on wire is corrupt, or it''s corrupt
after the driver process it, I check all the dtrace probes, and found following
dtrace probes may help: ip_input:ipInReceives, do I cannot find the detailed
description about ipInReceives, and how to get ip header checksum from it,
> could anyone share your experience on it?
>
> If anyone have similar dtrace script to troubeshooting IP/UDP checksum
error
> issues, could you please also share it?
If your debugging checksum issues, you might be interested in the
following thread on network-discuss:
http://www.opensolaris.org/jive/thread.jspa?threadID=36198&tstart=0
Garrett has determind that the hme driver (and possibly others) is not
checksumming data in some cases, and his replies to the list may be
useful for your analysis. It shounds like a fix for this issue will
benefit all, so you should jump into the conversation if you have any
thoughts.
Hope this helps,
- Ryan
--
UNIX Administrator
http://prefetch.net