Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!swrinde!elroy.jpl.nasa.gov!ames!usenet.cisco.com!iverson From: iverson@cisco.com (Tim Iverson) Newsgroups: comp.unix.bsd.freebsd.misc,comp.protocols.ppp Subject: Re: FreeBSD user-level PPP (iijppp) times out Date: 25 Jun 1996 01:19:05 GMT Organization: cisco Lines: 27 Message-ID: <4qneq9$h72@cronkite.cisco.com> References: <31CD508E.3394@cc.odu.edu> <4qk9dg$9hc@uriah.heep.sax.de> <31CE986C.2534@cc.odu.edu> NNTP-Posting-Host: rottweiler.cisco.com Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:22079 comp.protocols.ppp:14364 In article <31CE986C.2534@cc.odu.edu>, Jonathan Sturges <jonathan@cc.odu.edu> wrote: |J Wunsch wrote: |> |> Have you adjusted the idle time from the config file? | |Yes, I've added 'set timeout 0' to the script for the server I'm using. |Also, I additionally have tried issuing the timeout command at the PPP |command prompt prior to dialing my server. | |> I found that resetting the idle time to a new value while a connection |> is already active is apparently not supported (though you don't get an |> error message, and the program pretends it would use the new idle time |> -- but it simply doesn't). It works for me. I'm using 2.1 release. I found that there seems to be just one timeout value. So, if you set timeout from the command line interface, but your dialing script has a timeout value, the dialing timeout becomes the new timeout. This caused a minor problem for me -- my dialing timeout was set for 15 seconds, so my PPP sessions were quite short. ;-) I worked around this by setting the timeout again in the linkup file. I never tried '0', I'm just using a very large number. - Tim Iverson iverson@lionheart.com