Below are three examples of tcpdump complaining about truncated-ip,
whatever that is. Is this a problem? It doesn't seem to impact my
connection negatively. I am getting these when using a plain-vanilla
openssh client to connect to an ssh-1.2.27 server.
inbetween:~# tcpdump -i eth1 | grep truncated
tcpdump: listening on eth1
01:45:30.454190 truncated-ip - 10 bytes missing!velius.chaos2.org.ssh >
c392100-a.crvlls1.or.home.com.64080: P 3169:3433(264) ack 1580 win 32120
<nop,nop,timestamp 29956970 1187150> (DF)
01:45:40.501069 truncated-ip - 186 bytes missing!velius.chaos2.org.ssh >
c392100-a.crvlls1.or.home.com.64080: P 5809:6249(440) ack 2840 win 32120
<nop,nop,timestamp 29957969 1188151> (DF)
01:45:42.327067 truncated-ip - 274 bytes missing!velius.chaos2.org.ssh >
c392100-a.crvlls1.or.home.com.64080: P 6337:6865(528) ack 3120 win 32120
<nop,nop,timestamp 29958151 1188333> (DF)
Thanks,
-Jacob
--
"Heh. You mean this is Stef's source code?"
-User Friendly
whatever that is. Is this a problem? It doesn't seem to impact my
connection negatively. I am getting these when using a plain-vanilla
openssh client to connect to an ssh-1.2.27 server.
inbetween:~# tcpdump -i eth1 | grep truncated
tcpdump: listening on eth1
01:45:30.454190 truncated-ip - 10 bytes missing!velius.chaos2.org.ssh >
c392100-a.crvlls1.or.home.com.64080: P 3169:3433(264) ack 1580 win 32120
<nop,nop,timestamp 29956970 1187150> (DF)
01:45:40.501069 truncated-ip - 186 bytes missing!velius.chaos2.org.ssh >
c392100-a.crvlls1.or.home.com.64080: P 5809:6249(440) ack 2840 win 32120
<nop,nop,timestamp 29957969 1188151> (DF)
01:45:42.327067 truncated-ip - 274 bytes missing!velius.chaos2.org.ssh >
c392100-a.crvlls1.or.home.com.64080: P 6337:6865(528) ack 3120 win 32120
<nop,nop,timestamp 29958151 1188333> (DF)
Thanks,
-Jacob
--
"Heh. You mean this is Stef's source code?"
-User Friendly