I just got started with PacBell's ADSL package and am using their Enternet client to connect since they use PPPOE. I was just wondering what option to use so that pppd doesn't disconnect after be idle. I looked at demand, persist, and idle but it appears that idle is the only one that would apply. I see that you can use demand and persist but I'd rather have the connection stay up continually. The only thing I see to do is to set idle to a really long period. Is there a better solution? Thanks, Greg -- 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/
Hi, Greg Thomas wrote:
I just got started with PacBell's ADSL package and am using their Enternet client to connect since they use PPPOE. I was just wondering what option to use so that pppd doesn't disconnect after be idle. I looked at demand, persist, and idle but it appears that idle is the only one that would apply. I see that you can use demand and persist but I'd rather have the connection stay up continually. The only thing I see to do is to set idle to a really long period. Is there a better solution?
Thanks, Greg
You could create a small shell script that sends one ping to some server when the connection is up, and have it executed periodically using crontab. That way you can simulate somebody is actually using the connection and you won't be logged out. Bye, Martijn -- 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/
Greg Thomas wrote:
I just got started with PacBell's ADSL package and am using their Enternet client to connect since they use PPPOE. I was just wondering what option to use so that pppd doesn't disconnect after be idle. I looked at demand, persist, and idle but it appears that idle is the only one that would apply. I see that you can use demand and persist but I'd rather have the connection stay up continually. The only thing I see to do is to set idle to a really long period. Is there a better solution?
Which client are you using? IMHO I think the problems are on the ISP end-( I routinely keep my connection here up 3weeks or so using Jamal's client. Supposedly this current version of the client may be better. I've been using PPPoE since my ISP switched over last year [Oct I think] it's okay. If they could ever get things stable so the connection doesn't drop then it would be virtually equal to a static connection. Nick -- -------------------------------------------------- Nick Zentena "Microsoft has unjustifiably jeopardized the stability and security of the operating system." U.S. District Judge Thomas Penfield Jackson Nov 5/1999 -------------------------------------------------- -- 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/
On Mon, 6 Mar 2000, Nick Zentena wrote:
Greg Thomas wrote:
I just got started with PacBell's ADSL package and am using their Enternet client to connect since they use PPPOE. I was just wondering what option to use so that pppd doesn't disconnect after be idle. I looked at demand, persist, and idle but it appears that idle is the only one that would apply. I see that you can use demand and persist but I'd rather have the connection stay up continually. The only thing I see to do is to set idle to a really long period. Is there a better solution?
Which client are you using? IMHO I think the problems are on the ISP end-( I routinely keep my connection here up 3weeks or so using Jamal's client. Supposedly this current version of the client may be better. I've been using PPPoE since my ISP switched over last year [Oct I think] it's okay. If they could ever get things stable so the connection doesn't drop then it would be virtually equal to a static connection.
I'm using the Enternet client that Pacbell supplies. I was quite happy that they supported Linux. Anyway, with this client it's definitely pppd that shuts down the connection. With Jamal's client do I have to patch and re-compile the kernel? I'm running SuSE 6.3 and 2.2.13. Thanks, Greg -- 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/
Greg Thomas wrote:
I'm using the Enternet client that Pacbell supplies. I was quite happy that they supported Linux. Anyway, with this client it's definitely pppd that shuts down the connection. With Jamal's client do I have to patch and re-compile the kernel? I'm running SuSE 6.3 and 2.2.13.
Well there is Linux support and there is Linux support. My ISP provides a Linux client also. I think the company name is something like NTS and the product is called something like Ethernet [spelling??] I don't know anybody sane using the thing. At best it's a system hog at worst it's impossible to get working. SuSE ships with Jamal's client so I'm guessing the stock SuSE kernel includes support but I'm using a self compiled kernel so I don't know. Actually PPPoE is handled by the firewall machine which is still 6.1. Maybe SuSE could pipe up and tells us if it's in the stock 6.3 kernel. You might want to try adding the following to your /etc/ppp/options file lcp-echo-interval 240 lcp-echo-failure 3 # test section lcp-restart 1000 I don't think pppd will ever shutdown the link on it's own. What is likely happening is it isn't getting any response from the other end so it gives up and shutdown. Post a section of your logs. The above few lines might help. Nick -- -------------------------------------------------- Nick Zentena "Microsoft has unjustifiably jeopardized the stability and security of the operating system." U.S. District Judge Thomas Penfield Jackson Nov 5/1999 -------------------------------------------------- -- 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/
On Mon, 6 Mar 2000, Nick Zentena wrote:
Greg Thomas wrote:
I'm using the Enternet client that Pacbell supplies. I was quite happy that they supported Linux. Anyway, with this client it's definitely pppd that shuts down the connection. With Jamal's client do I have to patch and re-compile the kernel? I'm running SuSE 6.3 and 2.2.13.
Well there is Linux support and there is Linux support. My ISP provides a Linux client also. I think the company name is something like NTS and the product is called something like Ethernet [spelling??] I don't know anybody sane using the thing. At best it's a system hog at worst it's impossible to get working.
I have a feeling it's the same client I have.
SuSE ships with Jamal's client so I'm guessing the stock SuSE kernel includes support but I'm using a self compiled kernel so I don't know. Actually PPPoE is handled by the firewall machine which is still 6.1. Maybe SuSE could pipe up and tells us if it's in the stock 6.3 kernel.
When I tried Jamal's I got a "Can't locate module char-major-144".
You might want to try adding the following to your /etc/ppp/options file
lcp-echo-interval 240 lcp-echo-failure 3 # test section lcp-restart 1000
I don't think pppd will ever shutdown the link on it's own. What is likely happening is it isn't getting any response from the other end so it gives up and shutdown. Post a section of your logs. The above few lines might help.
Ok, I understand a little better now. Of the above I still don't understand what the lcp-restart does? Here's my log the last time I got disconnected: Mar 6 20:31:16 hominy pppd[8563]: sent [LCP EchoReq id=0x1b magic=0x288d9cff] Mar 6 20:31:46 hominy pppd[8563]: sent [LCP EchoReq id=0x1c magic=0x288d9cff] Mar 6 20:32:16 hominy pppd[8563]: sent [LCP EchoReq id=0x1d magic=0x288d9cff] Mar 6 20:32:46 hominy pppd[8563]: sent [LCP EchoReq id=0x1e magic=0x288d9cff] Mar 6 20:33:16 hominy pppd[8563]: No response to 4 echo-requests Mar 6 20:33:16 hominy pppd[8563]: Serial link appears to be disconnected. Mar 6 20:33:16 hominy pppd[8563]: Script /etc/ppp/ip-down started (pid 8905) Mar 6 20:33:16 hominy pppd[8563]: sent [LCP TermReq id=0x3 "Peer not responding"] Mar 6 20:33:16 hominy pppd[8563]: Script /etc/ppp/ip-down finished (pid 8905), status = 0x0 Mar 6 20:33:19 hominy pppd[8563]: sent [LCP TermReq id=0x4 "Peer not responding "] Mar 6 20:33:22 hominy pppd[8563]: Connection terminated. Mar 6 20:33:22 hominy pppd[8563]: Connect time 15.6 minutes. Mar 6 20:33:22 hominy pppd[8563]: Sent 420558 bytes, received 15182284 bytes. Mar 6 20:33:23 hominy pppd[8563]: Exit. I'd really like to get this reliable so my wife can just log on and check her e-mail without worrying whether the link is down. Thanks, Greg -- 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/
Greg Thomas wrote:
SuSE ships with Jamal's client so I'm guessing the stock SuSE kernel includes support but I'm using a self compiled kernel so I don't know. Actually PPPoE is handled by the firewall machine which is still 6.1. Maybe SuSE could pipe up and tells us if it's in the stock 6.3 kernel.
When I tried Jamal's I got a "Can't locate module char-major-144".
I don't know what char-major-144 is. It sounds familar. Usually most people get a 108. 108 is the new ppp number I think. Did it work when you tried it? I sort of ignore warning messages if it works-)
Ok, I understand a little better now. Of the above I still don't understand what the lcp-restart does? Here's my log the last time I got disconnected:
The lines I included are basically what some of the people using the system here have settled on. I just increased the numbers a little in hopes of improving things. Looking at your log what happens is what happens to us. The system "forgets" to send the LCP stuff. Your end finally gives up and decides that the ISP is dead. I get the impression our ISP was one of the first to switch over to PPPoE. That's why at least four different clients have come out of the people on this ISP.
I'd really like to get this reliable so my wife can just log on and check her e-mail without worrying whether the link is down.
I know the feeling. You can supposedly setup PPP to automatically restart. I've had no luck in getting the various files in /etc/ppp to work right. But then my link is stable enough that I haven't tried too much. Take a look at the roaring penguin client. It supposedly comes with a bunch of stuff to make it fairly painless to setup. http://www.suse.de/~bk/PPPoE-project.html Nick -- -------------------------------------------------- Nick Zentena "Microsoft has unjustifiably jeopardized the stability and security of the operating system." U.S. District Judge Thomas Penfield Jackson Nov 5/1999 -------------------------------------------------- -- 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/
participants (3)
-
ethant＠earthlink.net -
Martijn.van.den.Burg＠asml.nl -
zentena＠hophead.dyndns.org