> Levente Farkas wrote:

> > > Again, the ping in the package netkit-base-0.10-29.src.rpm from the Red
> > > Hat 6.0 distribution does not have the "wrong data byte #8" problem on
> > > i386.
> > 
> > have you heard about :
> > ftp://ftp.redhat.com/pub/redhat/updates/6.0/i386/netkit-base-0.10-31.i386.r
> pm
> > 
> 
> Yes.
> 

Good. it's broken, on Intel.

[summer@possum summer]$ rpm -qf `which ping`;ping os2 -c2
netkit-base-0.10-31
PING os2.os2.ami.com.au (203.55.31.51) from 192.168.1.6 : 56 data bytes
64 bytes from 203.55.31.51: icmp_seq=2 ttl=62 time=1810.3 ms
64 bytes from 203.55.31.51: icmp_seq=3 ttl=62 time=2690.5 ms

--- os2.os2.ami.com.au ping statistics ---
4 packets transmitted, 2 packets received, 50% packet loss
round-trip min/avg/max = 1810.3/2250.4/2690.5 ms
[summer@possum summer]$ rpm -qf `which ping`;ping os2 -c8
netkit-base-0.10-31
PING os2.os2.ami.com.au (203.55.31.51) from 192.168.1.6 : 56 data bytes
64 bytes from 203.55.31.51: icmp_seq=0 ttl=62 time=5165.9 ms
wrong data byte #8 should be 0xd1 but was 0xcc
        cc 9d cc 37 f7 5d 3 0 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 
1c 1d 1e 1f
        20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 
64 bytes from 203.55.31.51: icmp_seq=1 ttl=62 time=4811.2 ms
wrong data byte #8 should be 0xd1 but was 0xcd
        cd 9d cc 37 3 4b 3 0 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 
1c 1d 1e 1f
        20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 
64 bytes from 203.55.31.51: icmp_seq=2 ttl=62 time=4221.0 ms
wrong data byte #8 should be 0xd2 but was 0xce
        ce 9d cc 37 b 4b 3 0 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 
1c 1d 1e 1f
        20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 
64 bytes from 203.55.31.51: icmp_seq=3 ttl=62 time=3881.6 ms
wrong data byte #8 should be 0xd2 but was 0xcf
        cf 9d cc 37 b 4b 3 0 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 
1c 1d 1e 1f
        20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 
64 bytes from 203.55.31.51: icmp_seq=4 ttl=62 time=3421.3 ms
wrong data byte #8 should be 0xd3 but was 0xd0
        d0 9d cc 37 b 4b 3 0 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 
1c 1d 1e 1f
        20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 
64 bytes from 203.55.31.51: icmp_seq=5 ttl=62 time=3452.5 ms
wrong data byte #8 should be 0xd3 but was 0xd1
        d1 9d cc 37 fa 4a 3 0 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 
1c 1d 1e 1f
        20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 
64 bytes from 203.55.31.51: icmp_seq=6 ttl=62 time=2991.2 ms
wrong data byte #8 should be 0xd3 but was 0xd2
        d2 9d cc 37 1 4b 3 0 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 
1c 1d 1e 1f
        20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 
64 bytes from 203.55.31.51: icmp_seq=7 ttl=62 time=2000.8 ms

--- os2.os2.ami.com.au ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max = 2000.8/3743.1/5165.9 ms
[summer@possum summer]$ 

-- 
Cheers
John Summerfield
http://os2.ami.com.au/os2/ for OS/2 support.
Configuration, networking, combined IBM ftpsites index.


-- 
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Reply via email to