> I'm running PPP 3.1 (/usr/sbin/ppp) on OpenBSD 3.7 / i386. Every now
> and then, I run into a problem in which the chat script stops working
> in -auto mode:
> Dec 20 20:45:08 wally ppp[20296]: tun0: Chat: Expect(650): CONNECT
> 115200
> Dec 20 20:45:21 wally ppp[20296]: tun0: Chat: Expect timeout
Just as a followup to my own question - it looks as if the value being
used for the chat timeout is about 100 times too small. I don't know if
this means other timeouts are calculated incorrectly as well. Maybe the
calculation of TICKUNIT or SECTICKS is being done wrong in timer.h?
Dec 27 18:34:35 wally ppp[17586]: Warning: ---- Begin of Timer Service
List---
Dec 27 18:34:35 wally ppp[17586]: Warning: physical throughput
timer[0x3c04b068]
: freq = 1.00s, next = 0.00s, state = running
Dec 27 18:34:35 wally ppp[17586]: Warning: chat timeout
timer[0x3c037ab4]: freq
= 650.00s, next = 650.00s, state = running
Dec 27 18:34:35 wally ppp[17586]: Warning: ---- End of Timer Service
List ---
Dec 27 18:34:35 wally ppp[17586]: Warning: timer_Start: Inserting
physical throu
ghput timer[0x3c04b068] before chat timeout timer[0x3c037ab4], delta =
10
Dec 27 18:34:36 wally ppp[17586]: Warning: ---- Begin of Timer Service
List---
Dec 27 18:34:36 wally ppp[17586]: Warning: physical throughput
timer[0x3c04b068]
: freq = 1.00s, next = 0.00s, state = running
Dec 27 18:34:36 wally ppp[17586]: Warning: chat timeout
timer[0x3c037ab4]: freq
= 650.00s, next = 521.80s, state = running
Dec 27 18:34:36 wally ppp[17586]: Warning: ---- End of Timer Service
List ---
Obviously, I can't have gone through (650-521.8) seconds in between the
two timestamps (18:34:35 and 18:34:36). At any rate, if anyone else is
running into this problem, a user workaround is to put an insanely huge
timeout in your chat script. Mine is currently 6500 (which should be
nearly forever, but appears to be around 6.5 seconds).
Andrew Jr.
Just $16.99/mo. or less.
dsl.yahoo.com
