Flood ping dups packets

QNX Newsgroups (Archives) qdn.public.qnxrtp.os
1

Why is io-net duplicating packets under load? (QNX 6.1, io-net -ptcpip)
I see the same effect over an ethernet interface (rather than loopback).

$ ping -l10 localhost
PING localhost.localdomain (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=1 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=1 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=1 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=5 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=6 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=7 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=8 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=9 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=10 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=11 ttl=255 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=12 ttl=255 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=13 ttl=255 time=0 ms

Cheers,
Shaun

2

It’s an endian bug in our ping. They’re obviously not dups
as the icmp_seq numbers are correct. Thanks for the catch.

-seanb

Shaun Jackman <sjackman@nospam.vortek.com> wrote:

Why is io-net duplicating packets under load? (QNX 6.1, io-net -ptcpip)
I see the same effect over an ethernet interface (rather than loopback).

$ ping -l10 localhost
PING localhost.localdomain (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=1 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=1 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=1 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=5 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=6 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=7 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=8 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=9 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=10 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=11 ttl=255 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=12 ttl=255 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=13 ttl=255 time=0 ms

Cheers,
Shaun

3

“Sean Boudreau” <seanb@qnx.com> wrote in message
news:aet2bq$lv8$1@nntp.qnx.com…

It’s an endian bug in our ping. They’re obviously not dups
as the icmp_seq numbers are correct. Thanks for the catch.

I tried it with QNX4 and it showed the same problem. I’m assuming the
ping sources are the same for QNX4 and Neutrino but just in case :wink:

-seanb

Shaun Jackman <> sjackman@nospam.vortek.com> > wrote:
Why is io-net duplicating packets under load? (QNX 6.1, io-net -ptcpip)
I see the same effect over an ethernet interface (rather than loopback).

$ ping -l10 localhost
PING localhost.localdomain (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=1 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=1 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=1 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=5 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=6 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=7 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=8 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=9 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=10 ttl=255 time=1 ms (DUP!)
64 bytes from 127.0.0.1: icmp_seq=11 ttl=255 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=12 ttl=255 time=0 ms
64 bytes from 127.0.0.1: icmp_seq=13 ttl=255 time=0 ms

Cheers,
Shaun