[plug] ppp ping problem

[John Summerfield]

> 
> Greetings,
> 
> Has anyone else come across this problem?  The packets do indeed go out at
> 1 second intervals, as verified by the modem lights, but arrive back in
> bursts, typically 8-10 at a time.

I have seen it and it's always occurred when my modem's busy. On one 
occasion I lost several packets: those that were returned had reported 
times over 20 seconds. On that occasion, the number of packets lost was 
pretty constant: if I sent three, three were lost while if I sent 20, 
three were lost.


> 
> This occurs at intervals of 2-4 weeks and usually resolves itself by the
> modem dropping out.  I have seen it with different modems, different
> kernels, different ppp versions and sometimes it has even involved a
> Portmaster at the other end. 

I have also had my modem hang up (four times today). It's cheap (Banksia) 
and seems to dislike some of the Netcomms at the other end (a problem 
acknowledged by Banksia). Often this is preceded by slow/no response.

The box at the other end is OS/2: I've been running OS/2 and Linux 
starting from RH 5.0 (kernel 2.0.32 I think) and most kernels to 2.2.9 
(2.2.10 is waiting for the next reboot).


> 
> elm:# ping fred
> PING fred (192.168.2.1): 56 data bytes
> 64 bytes from 192.168.2.1: icmp_seq=0 ttl=255 time=6541.4 ms
> 64 bytes from 192.168.2.1: icmp_seq=1 ttl=255 time=5570.9 ms
> 64 bytes from 192.168.2.1: icmp_seq=2 ttl=255 time=4671.0 ms
> 64 bytes from 192.168.2.1: icmp_seq=3 ttl=255 time=3691.5 ms
> 64 bytes from 192.168.2.1: icmp_seq=4 ttl=255 time=2700.8 ms
> 64 bytes from 192.168.2.1: icmp_seq=5 ttl=255 time=1721.4 ms
> 64 bytes from 192.168.2.1: icmp_seq=6 ttl=255 time=731.3 ms
> 64 bytes from 192.168.2.1: icmp_seq=7 ttl=255 time=120.6 ms
> 64 bytes from 192.168.2.1: icmp_seq=8 ttl=255 time=7731.2 ms
> 64 bytes from 192.168.2.1: icmp_seq=9 ttl=255 time=6751.1 ms
> 64 bytes from 192.168.2.1: icmp_seq=10 ttl=255 time=5781.0 ms
> 64 bytes from 192.168.2.1: icmp_seq=11 ttl=255 time=4881.6 ms
> 64 bytes from 192.168.2.1: icmp_seq=12 ttl=255 time=3890.8 ms
> 64 bytes from 192.168.2.1: icmp_seq=13 ttl=255 time=2921.5 ms
> 64 bytes from 192.168.2.1: icmp_seq=14 ttl=255 time=1930.7 ms
> 64 bytes from 192.168.2.1: icmp_seq=15 ttl=255 time=941.3 ms
> 64 bytes from 192.168.2.1: icmp_seq=16 ttl=255 time=110.6 ms
> 
> Is this worthy of involving the Linux Heavyweights at linux-net?
> 
> Lindsay
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Lindsay Allen   <allen at cleo.murdoch.edu.au>  Perth, Western Australia
> voice +61 8 9316 2486    32.0125S 115.8445E    vk6lj     Debian Linux
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> 

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