Re: [info@ruediger-kuhlmann.de: [M68k-build] hydra and oddities... ehm... not eventities]
>--[Richard Zidlicky]--<Richard.Zidlicky@stud.informatik.uni-erlangen.de>
Mail-Followup-To: m68k-build@nocrew.org
I am on this list. Really. REALLY.
> > In other words: Packets get lost, if they have the wrong length modulo 2.
> try whether ping -s shows the same behaviour.
Not that reproducable, but yes.
ipmsun1:~# ping -s 60 proxy1.rz.uni-karlsruhe.de
PING proxy1.rz.uni-karlsruhe.de (129.13.64.201): 60 data bytes
68 bytes from 129.13.64.201: icmp_seq=0 ttl=253 time=19.8 ms
68 bytes from 129.13.64.201: icmp_seq=1 ttl=253 time=3.1 ms
--- proxy1.rz.uni-karlsruhe.de ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 3.1/11.4/19.8 ms
ipmsun1:~# ping -s 61 proxy1.rz.uni-karlsruhe.de
PING proxy1.rz.uni-karlsruhe.de (129.13.64.201): 61 data bytes
--- proxy1.rz.uni-karlsruhe.de ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
ipmsun1:~# ping -s 60 proxy1.rz.uni-karlsruhe.de
PING proxy1.rz.uni-karlsruhe.de (129.13.64.201): 60 data bytes
68 bytes from 129.13.64.201: icmp_seq=0 ttl=253 time=5.3 ms
68 bytes from 129.13.64.201: icmp_seq=1 ttl=253 time=5.4 ms
68 bytes from 129.13.64.201: icmp_seq=2 ttl=253 time=2.8 ms
--- proxy1.rz.uni-karlsruhe.de ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 2.8/4.5/5.4 ms
ipmsun1:~# ping -s 61 proxy1.rz.uni-karlsruhe.de
PING proxy1.rz.uni-karlsruhe.de (129.13.64.201): 61 data bytes
69 bytes from 129.13.64.201: icmp_seq=1 ttl=253 time=3.3 ms
69 bytes from 129.13.64.201: icmp_seq=2 ttl=253 time=2.3 ms
69 bytes from 129.13.64.201: icmp_seq=3 ttl=253 time=2.6 ms
69 bytes from 129.13.64.201: icmp_seq=4 ttl=253 time=2.3 ms
--- proxy1.rz.uni-karlsruhe.de ping statistics ---
5 packets transmitted, 4 packets received, 20% packet loss
round-trip min/avg/max = 2.3/2.6/3.3 ms
ipmsun1:~# ping -s 62 proxy1.rz.uni-karlsruhe.de
PING proxy1.rz.uni-karlsruhe.de (129.13.64.201): 62 data bytes
70 bytes from 129.13.64.201: icmp_seq=0 ttl=253 time=5.2 ms
70 bytes from 129.13.64.201: icmp_seq=1 ttl=253 time=2.4 ms
--- proxy1.rz.uni-karlsruhe.de ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 2.4/3.8/5.2 ms
ipmsun1:~# ping -s 65 proxy1.rz.uni-karlsruhe.de
PING proxy1.rz.uni-karlsruhe.de (129.13.64.201): 65 data bytes
--- proxy1.rz.uni-karlsruhe.de ping statistics ---
7 packets transmitted, 0 packets received, 100% packet loss
ipmsun1:~#
> > Now, the 21:42:06.313999 packet claims it length to be 3b = 59 bytes, but in
> > reality, 60 bytes are send! So when heise ack's 20 bytes of user data,
> > something must have gotten confused as only 19 bytes where supposed to be
> > sent - there are no further packets sent.
> 20 or 19, ethernet will xmit at least 64 so I don't see how the problem
> can be at the ethernet level.
Fact is that the packet emitted is in fact shorter. And those 19/20 bytes
are the payload, as stated the complete IP packet is 59/60 bytes long. If
tcpdump shows it is longer, then it _is_ longer. And I have seen packets of
odd length from other computers.
Yours, Rüdiger.
--
A "No" uttered from deepest conviction is better and greater than a
"Yes" merely uttered to please, or what is worse, to avoid trouble.
-- Mahatma Ghandi
Reply to: