Hi, Most of the ppp problems are caused by the options not set correctly for your usage. I found this out the hard way. most of the options are covered in the man pppd. As for the link time out see if you have idle set. From the man page:- idle n Specifies that pppd should disconnect if the link is idle for n seconds. The link is idle when no data packets (i.e. IP packets) are being sent or received. Note: it is not advisable to use this option with the persist option without the demand option. If the active-filter option is given, data packets which are rejected by the specified activ ity filter also count as the link being idle. If you are using KPPP this option is set in the PPP section of the setup section of KPPP. Another important setting is the modem timeout. Found under the Device settings in KPPP. If the device times out before a full connection is made to an ISP and you are using PAP you will get the "8 bit unclear" problem appearing in your log file. I have noticed my ISP can take a considerable time to respond to my PAP requests for authorisiation during busy periods. If you need to keep a link up for a considerable time I suggest you run a script that pings your ISP once a minute. This will stop the timeouts from happening. Regards, Graham Smith On 27-Mar-2000 Graham Smith wrote:
Hi,
I believe it is part of the options settings. For instance in KPPP you can set the maximum connection timeout. I'm not sure which of name underwhich it appears in the options file. I will have a look at it in the morning for you. (Got to have a sleep at some stage).
One way round the problem is to ping the ISP every couple of minutes to prevent the link shutting down.
Regards
Graham Smith
On 27-Mar-2000 James Ogley wrote:
I'm trying to set up my Linux box to dial out - but I keep getting the ol' message of pppd daemon died unexpectedly.
This happened to me last night, right annoying, isn't it? I suspect that it might have something to do with your ISP closing the connection if you fulfill requirements to be classified as 'Idle' ie you may not have sent any connection requests on standard ports for xx seconds/minutes/hours/decades. Obviously something like this varies from ISP to ISP, but one way to get past it is to ping a remote host every minute or so while you're online. Either set a script to do it, or do it manually (advantage of the latter is you can do different ones - so it doesn't look like you're doing anything dodgy)
Or, and probably more likely to achieve the desired result, although less automate-able is to have an extra browser window open, and make occasional connecetions to random websites. More like to work as ISPs are more likely to monitor for connections on port 80 than any other port.
-- James Ogley, SuSE Linux UK Ltd - +44 (0) 20 8 387 4088 @ Work: ogley@suse.co.uk www.suse.co.uk @ Home: james@rubberturnip.org.uk www.rubberturnip.org.uk ICQ: 57374251 Slashdot: riggwelter (84180)
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/