Re: [SLE] Dial on Demand with smpppd
On Sun, 15 Jun 2003 04:16 am, BandiPat wrote:
I usually set mine for 30000 which seems to take care of such things.
Richard
=================
Or just to zero (0), if you want it to be infinite. It won't hangup until you tell it too.
Patrick
It is not just staying online until kicked off. I want it to reconnect, even without network activity, so the system stays connected 24/7. Jasmine -- Jasmine Davis - Photo Girl www.photo-girl.com Registered Linux User Since August 1999, No: 218292 -------------------------->> Welcome to SuSE Linux 8.2 i686 - Kernel 2.4.20-64GB-SMP hotgirls login: 11:07am up 19:10, 2 users, load average: 0.20, 0.10, 0.03
On Sat, 2003-06-14 at 20:11, Jasmine Davis wrote:
It is not just staying online until kicked off. I want it to reconnect, even without network activity, so the system stays connected 24/7.
Jasmine
That's a whole nuther thing, then. What usually happens is your ISP will automatically kick you off after a period of inactivity. Sometimes checking your email every 10 minutes or so will be all that is required to keep you online. However, some ISP's won't let that kind of activity count. Some even do a disconnect for you every four hours or so regardless of what you are doing. One partial solution would be to automatically reconnect whenever there is a disconnect. I believe that is the Dial on Demand that you can select in the Connection Parameters page of Yast Modem setup. Perhaps someone who still uses a modem can better help you. Have you given any thought to getting broadband, like cable, or ADSL to stay online permanently? For me cable is the real answer. Always on, fast and I can use the phone at the same time. Richard
On Sun, 15 Jun 2003 01:28 pm, Richard wrote:
On Sat, 2003-06-14 at 20:11, Jasmine Davis wrote:
It is not just staying online until kicked off. I want it to reconnect, even without network activity, so the system stays connected 24/7.
Jasmine
That's a whole nuther thing, then. What usually happens is your ISP will automatically kick you off after a period of inactivity. Sometimes checking your email every 10 minutes or so will be all that is required to keep you online. However, some ISP's won't let that kind of activity count. Some even do a disconnect for you every four hours or so regardless of what you are doing.
The system in question here uses a permanent connection for an office mailserver, so it is importent for it to stay online & the ISP knows that. The connection that is used is ADSL & the ISP does not kick the line off unless somthing down their end (like Telstra) pull the plug for maintenace or more often, other failure. It is just when it gets kicked off, it has trouble getting back on.
One partial solution would be to automatically reconnect whenever there is a disconnect. I believe that is the Dial on Demand that you can select in the Connection Parameters page of Yast Modem setup. Perhaps someone who still uses a modem can better help you.
I have tried AUTO_RECONNECT='yes' in the provider file but this does not seem to do anything. I even set a cron job to ping an outside source every 10 minutes, but this does not seem to get it back online, most times, the system has to be restarted for it to reconnect.
Have you given any thought to getting broadband, like cable, or ADSL to stay online permanently? For me cable is the real answer. Always on, fast and I can use the phone at the same time.
As I said before, this is ADSL, but in AU, it is pretty unreliable for staying up. Jasmine -- Jasmine Davis - Photo Girl www.photo-girl.com Registered Linux User Since August 1999, No: 218292 -------------------------->> Welcome to SuSE Linux 8.2 i686 - Kernel 2.4.20-64GB-SMP hotgirls login: 9:15am up 1 day 17:18, 2 users, load average: 0.82, 0.25, 0.09
On Sunday 15 June 2003 15:23, Jasmine Davis wrote:
On Sun, 15 Jun 2003 01:28 pm, Richard wrote:
On Sat, 2003-06-14 at 20:11, Jasmine Davis wrote:
It is not just staying online until kicked off. I want it to reconnect, even without network activity, so the system stays connected 24/7.
Jasmine
That's a whole nuther thing, then. What usually happens is your ISP will automatically kick you off after a period of inactivity. Sometimes checking your email every 10 minutes or so will be all that is required to keep you online. However, some ISP's won't let that kind of activity count. Some even do a disconnect for you every four hours or so regardless of what you are doing.
The system in question here uses a permanent connection for an office mailserver, so it is importent for it to stay online & the ISP knows that.
The connection that is used is ADSL & the ISP does not kick the line off unless somthing down their end (like Telstra) pull the plug for maintenace or more often, other failure. It is just when it gets kicked off, it has trouble getting back on.
One partial solution would be to automatically reconnect whenever there is a disconnect. I believe that is the Dial on Demand that you can select in the Connection Parameters page of Yast Modem setup. Perhaps someone who still uses a modem can better help you.
I have tried AUTO_RECONNECT='yes' in the provider file but this does not seem to do anything. I even set a cron job to ping an outside source every 10 minutes, but this does not seem to get it back online, most times, the system has to be restarted for it to reconnect.
Have you given any thought to getting broadband, like cable, or ADSL to stay online permanently? For me cable is the real answer. Always on, fast and I can use the phone at the same time.
As I said before, this is ADSL, but in AU, it is pretty unreliable for staying up.
Refresh my memory... What version of SuSE are you running? I wonder if there is something flakey in SuSEs smpppd support. I had similar problems. I'm writing from Alaska but our company has a SuSE 8.1 server in Hobart Taz, on bigpond, and it used to disconnect all the time if we let it sit too long. We tried the dial on demand bit, and went round and round with that. We scheduled 3 ping every 3 minutes with crontab. We scheduled a cinternet redial every 15 minutes. It seems to do nothing if the link is already up, but did trigger dials if we indentionally shut doen the link and let cron trigger the following command: cinternet --start Our /etc/sysconfig/network/providers/dsl-provider0 file looks like this... ----- PROVIDER="DSL provider" DSLSUPPORTED="yes" MODEMSUPPORTED="no" ISDNSUPPORTED="no" USERNAME="XXXXXXXX@bigpond" PASSWORD="YYYYYYYY" IDLETIME="920" DEMAND="yes" DNS1="61.9.128.14" DNS2="61.9.128.15" ----- (yes we did have to hardwire thos DNS servers) And note we manually modified this file to get 920 in there because the yast page did not seem to like that value. With this combination of stuff it stays on line. I can't be sure just which of these is keeping the link alive, but its been up for over two months with no lan-side sourced traffic now (all inbound from the net). Hope this helps... ____________________________________ John Andersen
Refresh my memory... What version of SuSE are you running? I wonder if there is something flakey in SuSEs smpppd support. I had similar problems.
I'm writing from Alaska but our company has a SuSE 8.1 server in Hobart Taz, on bigpond, and it used to disconnect all the time if we let it sit too long. We tried the dial on demand bit, and went round and round with that.
We scheduled 3 ping every 3 minutes with crontab. We scheduled a cinternet redial every 15 minutes. It seems to do nothing if the link is already up, but did trigger dials if we indentionally shut doen the link and let cron trigger the following command: cinternet --start
Our /etc/sysconfig/network/providers/dsl-provider0 file looks like this... ----- PROVIDER="DSL provider" DSLSUPPORTED="yes" MODEMSUPPORTED="no" ISDNSUPPORTED="no" USERNAME="XXXXXXXX@bigpond" PASSWORD="YYYYYYYY" IDLETIME="920" DEMAND="yes" DNS1="61.9.128.14" DNS2="61.9.128.15" ----- (yes we did have to hardwire thos DNS servers) And note we manually modified this file to get 920 in there because the yast page did not seem to like that value.
With this combination of stuff it stays on line. I can't be sure just which of these is keeping the link alive, but its been up for over two months with no lan-side sourced traffic now (all inbound from the net).
Hope this helps...
____________________________________ John Andersen
The system runs SuSE 8.2 Professional. The provider file is pretty much the same as yours, except that the idle time is set to '0' for unlimited timeout. My experiance with the ADSL in Australia has been that it is pretty crappy for reliablity, with some weeks we get downtime every day sometimes upto a quite a few hours. I might disable the dial on demand & write a shell script that checks for connectivity & if down runs cinternet if it is down, then run it with a cron job. Jasmine -- Jasmine Davis - Photo Girl www.photo-girl.com Registered Linux User Since August 1999, No: 218292 -------------------------->> Welcome to SuSE Linux 8.2 i686 - Kernel 2.4.20-64GB-SMP hotgirls login: 9:51am up 1 day 17:54, 2 users, load average: 0.13, 0.16, 0.14
John Andersen wrote:
On Sunday 15 June 2003 15:23, Jasmine Davis wrote:
On Sun, 15 Jun 2003 01:28 pm, Richard wrote:
On Sat, 2003-06-14 at 20:11, Jasmine Davis wrote:
It is not just staying online until kicked off. I want it to reconnect, even without network activity, so the system stays connected 24/7.
Jasmine
That's a whole nuther thing, then. What usually happens is your ISP will automatically kick you off after a period of inactivity. Sometimes checking your email every 10 minutes or so will be all that is required to keep you online. However, some ISP's won't let that kind of activity count. Some even do a disconnect for you every four hours or so regardless of what you are doing.
You are correct about some ISPs not always counting email as a time. However, I think maybe using "netdate" to go get the time set by a script and cron might solve the problem. Besides setting the time correctly. In CST6DST/Houston, TX # # netdate - set date and time by ARPA Internet RFC 868 # netdate [ -v ] [ -l limit ] [ protocol ] hostname.. netdate tick.uh.edu navobs1.wustl.edu now.cis.okstate.edu The following will set hardware clock using linux time: hwclock --systohc Netdate is on SuSE's CDs -- 73 de Donn Washburn __ " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB / / __ __ __ __ __ __ __ 307 Savoy St. / /__ / / / \/ / / /_/ / \ \/ / Sugar Land, TX 77478 /_____/ /_/ /_/\__/ /_____/ /_/\_\ LL# 1.281.242.3256 a MSDOS Virus "Free Zone" OS Email: n5xwb@hal-pc.org Info: http://www.knoppix.net
I had this problem with ISDN handler for pppd, which terminates the call
even if you set long timeouts. I found that a cron job doing:
ping -c1 -t2 <url>
keeps the line alive.
Derek
----- Original Message -----
From: "Donn Washburn"
John Andersen wrote:
On Sunday 15 June 2003 15:23, Jasmine Davis wrote:
On Sun, 15 Jun 2003 01:28 pm, Richard wrote:
On Sat, 2003-06-14 at 20:11, Jasmine Davis wrote:
It is not just staying online until kicked off. I want it to
reconnect,
even without network activity, so the system stays connected 24/7.
Jasmine
That's a whole nuther thing, then. What usually happens is your ISP will automatically kick you off after a period of inactivity. Sometimes checking your email every 10 minutes or so will be all that is required to keep you online. However, some ISP's won't let that kind of activity count. Some even do a disconnect for you every four hours or so regardless of what you are doing.
You are correct about some ISPs not always counting email as a time. However, I think maybe using "netdate" to go get the time set by a script and cron might solve the problem. Besides setting the time correctly.
In CST6DST/Houston, TX
# # netdate - set date and time by ARPA Internet RFC 868 # netdate [ -v ] [ -l limit ] [ protocol ] hostname..
netdate tick.uh.edu navobs1.wustl.edu now.cis.okstate.edu
The following will set hardware clock using linux time:
hwclock --systohc
Netdate is on SuSE's CDs -- 73 de Donn Washburn __ " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB / / __ __ __ __ __ __ __ 307 Savoy St. / /__ / / / \/ / / /_/ / \ \/ / Sugar Land, TX 77478 /_____/ /_/ /_/\__/ /_____/ /_/\_\ LL# 1.281.242.3256 a MSDOS Virus "Free Zone" OS Email: n5xwb@hal-pc.org Info: http://www.knoppix.net
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Sunday 15 June 2003 18:23, Jasmine Davis wrote:
On Sat, 2003-06-14 at 20:11, Jasmine Davis wrote:
It is not just staying online until kicked off. I want it to reconnect, even without network activity, so the system stays connected 24/7.
Jasmine
That's a whole nuther thing, then. What usually happens is your ISP will automatically kick you off after a period of inactivity. Sometimes checking your email every 10 minutes or so will be all that is required to keep you online. However, some ISP's won't let that kind of activity count. Some even do a disconnect for you every four hours or so regardless of what you are doing.
The system in question here uses a permanent connection for an office mailserver, so it is importent for it to stay online & the ISP knows that.
The connection that is used is ADSL & the ISP does not kick the line off unless somthing down their end (like Telstra) pull the plug for maintenace or more often, other failure. It is just when it gets kicked off, it has trouble getting back on.
One partial solution would be to automatically reconnect whenever there is a disconnect. I believe that is the Dial on Demand that you can select in the Connection Parameters page of Yast Modem setup. Perhaps someone who still uses a modem can better help you.
I have tried AUTO_RECONNECT='yes' in the provider file but this does not seem to do anything. I even set a cron job to ping an outside source every 10 minutes, but this does not seem to get it back online, most times, the system has to be restarted for it to reconnect.
Have you given any thought to getting broadband, like cable, or ADSL to stay online permanently? For me cable is the real answer. Always on, fast and I can use the phone at the same time.
As I said before, this is ADSL, but in AU, it is pretty unreliable for staying up.
Woops, I misunderstood your question. I thought you were using a standard modem ppp connection. Sorry, It's been a couple of years since I tried the ADSL setup but as I recal it was pretty straight forward. I simply found the ADSL Howto and with SuSE 8.0 it worked fine til Ma Bell decided to kill the independent isp's in California. We redid it as ADSL ppoe per the HOWTO. Again pretty straight forward. I started with this HowTo: http://new.linuxnow.com/docs/content/ADSL/ADSL-3.html And the SuSE Administrator's guide has more info on ADSL and DSL setup at pp418-419. They say to "set the parameter DEMAND="yes" in /etc/sysconfig/network/providers/provider0 file then define an idle time via the variable IDLE-TIME="60". This way, an unused connection will be dropped after sixty seconds." Obviously setting the time to a large number would increase the timeout. Maybe a blank would disable the timeout. It's worth a try. Have you tried that yet? HTH< Richard
On 06/16/2003 07:23 AM, Jasmine Davis wrote:
The connection that is used is ADSL & the ISP does not kick the line off unless somthing down their end (like Telstra) pull the plug for maintenace or more often, other failure. It is just when it gets kicked off, it has trouble getting back on.
man pppd gives you a list of the options you could use. You could try to use persist in your /etc/ppp/peers/(your connection) file to explicitly tell it to reconnect on connection termination, or maybe debug to get more troubleshooting info. HTH. (BTW, DOD is supposed to already use persist.) -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
participants (6)
-
Derek Clifford -
Donn Washburn -
Jasmine Davis -
Joe Morris (NTM) -
John Andersen -
Richard