Re: [SLE] KInternet - How can I stay connected? - SOLVED
Ok I solved the problem, it was quiet simple actually. I went to yast2, and then to configure DSL connection (the one you should have gone through when you were setting up your system). Then go through the configuration you have there and make sure you have "On Boot" selected and the Idle time set to zero. Save changes, exit KInternet and when it asks you wether you want it to start next time say NO. Restart your computer and you should have a permanent internet connection without ever worring about KInternet again Hope it helps =) On Saturday 31 January 2004 1:34 pm, Tom Reagan wrote:
Mike, I have the same goal. Please let me know what you find out!
Thanks, Tom
Michael Yartsev <anijap@execulink.com> wrote: I have a DSL connection which works fine.
My question is, how can I make the connection stay alive even when I log out/ in to my account? (or another account e.g root)
And will the connection stay alive even when no user is logged into my machine? (@ the login screen).
I also want to disable the timeout option when no internet activity has been detected for a while, where can I disable that?
Why am I asking? I want to set up an apache web server and I want it to be up all the time even when no one's using the computer
It doesn't have to be KInternet anything else is welcome as long as it gets the job done.
Cheers, Mike
On Saturday 31 January 2004 14:42, Michael Yartsev wrote:
Ok I solved the problem, it was quiet simple actually.
I went to yast2, and then to configure DSL connection (the one you should have gone through when you were setting up your system). Then go through the configuration you have there and make sure you have "On Boot" selected and the Idle time set to zero.
Save changes, exit KInternet and when it asks you wether you want it to start next time say NO.
Restart your computer and you should have a permanent internet connection without ever worring about KInternet again
<SNIP> I am using an ISDN modem and sometimes --though not often-- the connection gets dropped and, unlike kppp, doesn't redail & continue. Is there a solution for this, also? ...CH
On Sun, 1 Feb 2004 07:51, C Hamel wrote:
I am using an ISDN modem and sometimes --though not often-- the connection gets dropped and, unlike kppp, doesn't redail & continue. Is there a solution for this, also?
...CH
I use the following script to reconnect an ADSL connection which falls over every now and then. It is run by CRON every 10 minutes. It is not the greatest script but it works. You may be able to adapt the script to suit. ------------------------------ Reconnect_DSL.sh ------------------------------ #!/bin/bash # # Script to check if ADSL is disconnected & try reconnecting # result=$(cinternet -i dsl0 -s | grep disconnect) if [ -n "$result" ] then cinternet -i dsl0 -A sleep 10 else exit 0 fi ____________________ EOF ______________________ -- Regards, Graham Smith ---------------------------------------------------------
On Saturday 31 January 2004 20:44, Graham Smith wrote: <SNIP>
I use the following script to reconnect an ADSL connection which falls over every now and then. It is run by CRON every 10 minutes. It is not the greatest script but it works.
You may be able to adapt the script to suit.
------------------------------ Reconnect_DSL.sh ------------------------------ #!/bin/bash # # Script to check if ADSL is disconnected & try reconnecting # result=$(cinternet -i dsl0 -s | grep disconnect) if [ -n "$result" ] then cinternet -i dsl0 -A sleep 10 else exit 0 fi ____________________ EOF ______________________
Many thanks for the script! I take it that the dsl0 represents the device. I understand some of the script, but I could use a little more commenting, since I am not all that script-savvy, yet --'yet' being key word, I hope. I haven't done any programming in roughly 20 years. :-\ Thanks!! ...CH
On Sun, 1 Feb 2004 14:47, C Hamel wrote: #!/bin/bash
# # Script to check if ADSL is disconnected & try reconnecting # result=$(cinternet -i dsl0 -s | grep disconnect) Checks the status of device dsl0 for the word 'disconnect' and stores the result in a variable called 'result' if [ -n "$result" ] Test to see if the value is not NULL then OK the interface is down cinternet -i dsl0 -A Start the interface. sleep 10 else The interface is up - Just exit exit 0 fi ____________________ EOF ______________________
Many thanks for the script! I take it that the dsl0 represents the device. I understand some of the script, but I could use a little more commenting, since I am not all that script-savvy, yet --'yet' being key word, I hope. I haven't done any programming in roughly 20 years. :-\
Thanks!! ...CH
I suggest you look at the man page for cinternet for further details on it's command options. -- Regards, Graham Smith ---------------------------------------------------------
On Saturday 31 January 2004 23:29, Graham Smith wrote: <SNIP>
I suggest you look at the man page for cinternet for further details on it's command options.
Thanks for the added info! I shall do that! Rgds... ...CH
On Sunday 01 February 2004 20:16, C Hamel wrote:
On Saturday 31 January 2004 23:29, Graham Smith wrote: <SNIP>
I suggest you look at the man page for cinternet for further details on it's command options.
Thanks for the added info! I shall do that!
Rgds... ...CH
However, don't expect a great deal of success staying connected if it is a adsl line, as most providers knock you off for no obvious reason periodically. Sometimes this is ok, but if you expect connections from the outside its really irritating. By pinging some remote site one time every X minutes (where X is your ISP cutoff time) you can get around this. Also helps to turn on the reliability flag in the ping because some providers train their disconnect logic to ignore pings. -- _____________________________________ John Andersen
In my experience kinternet just plain sux. Back when I was using a modem I had the same issues with kinternet detecting idle time and disconnecting. This is a design 'feature' which is probably good if you suffer with timed local calls.I never did get it to work properly and used wvdial instead which is quite easy to setup. just set timeout to 0 in the config file. ----- Original Message ----- From: "John Andersen" <jsa@pen.homeip.net> To: <suse-linux-e@suse.com> Sent: Tuesday, February 03, 2004 5:44 PM Subject: Re: [SLE] KInternet - How can I stay connected? - SOLVED
On Sunday 01 February 2004 20:16, C Hamel wrote:
On Saturday 31 January 2004 23:29, Graham Smith wrote: <SNIP>
I suggest you look at the man page for cinternet for further details on it's command options.
Thanks for the added info! I shall do that!
Rgds... ...CH
However, don't expect a great deal of success staying connected if it is a adsl line, as most providers knock you off for no obvious reason periodically. Sometimes this is ok, but if you expect connections from the outside its really irritating.
By pinging some remote site one time every X minutes (where X is your ISP cutoff time) you can get around this. Also helps to turn on the reliability flag in the ping because some providers train their disconnect logic to ignore pings.
-- _____________________________________ John Andersen
-- 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 Tuesday 03 February 2004 01:33, robomort wrote:
In my experience kinternet just plain sux. Back when I was using a modem I had the same issues with kinternet detecting idle time and disconnecting. This is a design 'feature' which is probably good if you suffer with timed local calls.I never did get it to work properly and used wvdial instead which is quite easy to setup. just set timeout to 0 in the config file.
Yes, kinternet sucks, but cinternet can be cron'd to run as needed to reestablish connections. But your idea to set time out to 0 is not the problem I was mentioning. Timeout 0 ONLY prevents disconnects caused by your machine. Many adsl providers disconnect you from their end when there is no activity on the link. Nothing you can do about this other than to make sure there IS SOME activity every X minutes to prevent their watchdog from cutting you off. -- _____________________________________ John Andersen
Sorry for the misunderstanding, I could not find the root of the thread and I suppose I assumed you were having the same problem that I had. Strange setup you have with the adsl . With my ISP here in australia adsl connections are permanent 24/7 we even get a choice of static or dynamic IP. As for the ISP timeout issue I suppose you could get your mail client to check for mail at regular intervals I guess that would be fair usage ;) cheers Rob ----- Original Message ----- From: "John Andersen" <jsa@pen.homeip.net> To: <suse-linux-e@suse.com> Sent: Wednesday, February 04, 2004 4:39 AM Subject: Re: [SLE] KInternet - How can I stay connected? - SOLVED
On Tuesday 03 February 2004 01:33, robomort wrote:
In my experience kinternet just plain sux. Back when I was using a modem I had the same issues with kinternet detecting idle time and disconnecting. This is a design 'feature' which is probably good if you suffer with timed local calls.I never did get it to work properly and used wvdial instead which is quite easy to setup. just set timeout to 0 in the config file.
Yes, kinternet sucks, but cinternet can be cron'd to run as needed to reestablish connections.
But your idea to set time out to 0 is not the problem I was mentioning.
Timeout 0 ONLY prevents disconnects caused by your machine.
Many adsl providers disconnect you from their end when there is no activity on the link. Nothing you can do about this other than to make sure there IS SOME activity every X minutes to prevent their watchdog from cutting you off.
-- _____________________________________ John Andersen
-- 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 Tuesday 03 February 2004 14:03, robomort wrote:
Sorry for the misunderstanding, I could not find the root of the thread and I suppose I assumed you were having the same problem that I had. Strange setup you have with the adsl . With my ISP here in australia adsl connections are permanent 24/7 we even get a choice of static or dynamic IP. As for the ISP timeout issue I suppose you could get your mail client to check for mail at regular intervals I guess that would be fair usage ;)
Actually Rob, there in Aus was where I was having the problem. Bigpond (at least in Hobart) will drop you if idle for more than a few minutes. Now the first time our machine tried to check mail or do anything else cinternet would connect so fast you thought you were always connected. But our mailserver here in the states forwarded mail to our linux box on bigpond (using dyndns.org dynamic dns). But the linux machine connection was dumped by bigpond, so connection was impossible from the US. Only by forcing connections (we used ping in a cron job) every three minutes could we guarentee it would stay up, or re-connect if it went down for any reason. -- _____________________________________ John Andersen
On Tuesday 03 February 2004 09:44, John Andersen wrote:
Also helps to turn on the reliability flag in the ping because some providers train their disconnect logic to ignore pings
~ maybe using cron to activate time-daemon xntpd , is alternative ? -- best wishes ____________ sent on Linux ____________
participants (6)
-
C Hamel
-
Graham Smith
-
John Andersen
-
Michael Yartsev
-
pinto
-
robomort