Re: odd ppp performance

[Lee Bradshaw <lee@sectionIV.com>]

On Sun, Apr 23, 2000 at 06:04:49PM +0800, Lindsay Allen wrote:
> On Sun, 23 Apr 2000 kmself@ix.netcom.com wrote:
> 
>> On Sun, Apr 23, 2000 at 11:51:35AM +0800, Lindsay Allen wrote:
>> > mentor:# ping t99
>> > PING t99 t99.xxx.wa.edu.au (192.168.1.99): 56 data bytes
>> > 64 bytes from 192.168.1.99: icmp_seq=0 ttl=254 time=7441.6 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=1 ttl=254 time=6459.8 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=2 ttl=254 time=5474.5 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=3 ttl=254 time=4517.5 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=4 ttl=254 time=3525.3 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=5 ttl=254 time=2532.6 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=6 ttl=254 time=1542.5 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=7 ttl=254 time=552.7 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=8 ttl=254 time=7996.1 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=9 ttl=254 time=7037.2 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=10 ttl=254 time=6061.9 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=11 ttl=254 time=5071.6 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=12 ttl=254 time=4077.2 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=13 ttl=254 time=3082.3 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=14 ttl=254 time=2108.0 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=15 ttl=254 time=1116.9 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=16 ttl=254 time=128.5 ms
>> > 64 bytes from 192.168.1.99: icmp_seq=17 ttl=254 time=119.4 ms
> 
> This has occured with different Deb boxes and different ISPs.  Seems to me
> that it is either a ppp bug or a kernel bug but it has persisted over
> different versions of both.

It may be your isp. I've seen the problem where neither ppp nor the
kernel should have been involved.

At the time I was using an ethernet to ISDN router, so ppp wasn't
involved. The ISDN router was the default gateway, so I wasn't
bringing interfaces up and down and changing routes. The router would
bring up the isdn line if it saw traffic that needed to go off the local
net. If the connection got really slow I'd stop using it and/or force
the isdn connection to drop. If a brought it back up a couple minutes
later, everything was fine.

-- 
Lee Bradshaw                 lee@sectionIV.com (preferred)
Alantro Communications       lee@alantro.com