[2058] in linux-net channel archive

home help back first fref pref prev next nref lref last post

1.3.72 packet truncation in tcpdump

daemon@ATHENA.MIT.EDU (Bob Felderman)
Tue Mar 12 21:18:22 1996

Date: 	Tue, 12 Mar 96 14:04:48 PST
From: feldy@myri.com (Bob Felderman)
To: linux-net@vger.rutgers.edu

I'm using tcpdump3.0.2 with linux-1.3.72 to try
to look at the problems I'm seeing with TCP and UDP.
tcpdump is telling me that I have truncated packets.

12:25:15.841294 truncated-ip - 4138 bytes missing!leda.33314 > pandora.1131: udp 8192 (DF) (ttl 255, id 4626)
12:25:15.841294 truncated-ip - 4138 bytes missing!leda.33314 > pandora.1131: udp 8192 (DF) (ttl 255, id 4628)
12:25:15.851294 truncated-ip - 4138 bytes missing!leda.33314 > pandora.1131: udp 8192 (DF) (ttl 255, id 4630)
12:25:15.851294 truncated-ip - 4138 bytes missing!leda.33314 > pandora.1131: udp 8192 (DF) (ttl 255, id 4632)
12:25:15.851294 truncated-ip - 4138 bytes missing!leda.33314 > pandora.1131: udp 8192 (DF) (ttl 255, id 4633)
12:25:15.861294 truncated-ip - 4138 bytes missing!leda.33314 > pandora.1131: udp 8192 (DF) (ttl 255, id 4635)
12:25:15.861294 truncated-ip - 4138 bytes missing!leda.33314 > pandora.1131: udp 8192 (DF) (ttl 255, id 4637)


My question is, is this because the snooper is truncating data, or do
I have a real ip truncation? I don't see any error printk() in the
system log from the networking code.

Thoughts?


home help back first fref pref prev next nref lref last post