[opensuse] How to staying connected to the network after logging out from session?
Hello: I have openSUSE 11.2 with KDE 3.5.10. I am using kinterent for network connection. My setup in yast for network setting is: traditional method with ifup. The setting for DSL connection in yast are: - activate device on hotplug - enable device control for non-root user via kinternet is turned on After logging in an account kinternet automatically connects to the network, but if the user logs out the computer becomes disconnected. I would like the system to stay connected after the user logs out from his session. How can I achieve it? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/25/2010 11:57 AM, Istvan Gabor wrote:
After logging in an account kinternet automatically connects to the network, but if the user logs out the computer becomes disconnected. I would like the system to stay connected after the user logs out from his session. How can I achieve it?
Get rid of kinternet and use kcm_knemo to 'monitor' the network connection. (if it isn't installed, you can get kde3-knemo in the kde3 repository) To check: ls -al /opt/kde3/share/applications/kde/kcm_knemo.desktop kill kinternet (rt-click/exit) start knemo (either use the menu entry (I don't recall where it hides), or just 'alt+F2 kcmshell kcm_knemo') Then just configure it the way you like. (I hate the default graph colors...) Since you are using traditional ifup, the network connection should be established 'on boot' and stay established regardless of the desktop state. Make sure you have the connection set to 'on boot' in Yast. (first tab) Yast should restart the interface after changes, but if not, just issue an 'rcnetwork restart' -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2010. október 25. 22:37 napon "David C. Rankin"
On 10/25/2010 11:57 AM, Istvan Gabor wrote:
After logging in an account kinternet automatically connects to the network, but if the user logs out the computer becomes disconnected. I would like the system to stay connected after the user logs out from his session. How can I achieve it?
Get rid of kinternet and use kcm_knemo to 'monitor' the network connection. (if it isn't installed, you can get kde3-knemo in the kde3 repository) To check:
ls -al /opt/kde3/share/applications/kde/kcm_knemo.desktop
kill kinternet (rt-click/exit)
start knemo (either use the menu entry (I don't recall where it hides), or just 'alt+F2 kcmshell kcm_knemo') Then just configure it the way you like. (I hate the default graph colors...)
Since you are using traditional ifup, the network connection should be established 'on boot' and stay established regardless of the desktop state. Make sure you have the connection set to 'on boot' in Yast. (first tab)
Yast should restart the interface after changes, but if not, just issue an 'rcnetwork restart'
Hello David, Thank you for your help. I tried knemo and it works OK, but I would like to be able to turn off and on the network manually. It seems that with knemo I cannot do it. Or can it be configured like that? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/26/2010 03:42 PM, Istvan Gabor wrote:
Hello David,
Thank you for your help. I tried knemo and it works OK, but I would like to be able to turn off and on the network manually. It seems that with knemo I cannot do it. Or can it be configured like that?
Istvan, knemo just monitors the interface and cannot turn it on or off. I thought you wanted the network 'On' all the time. (that's what I do). That's why I suggested setting the interface to initialize 'on boot'. I have had nothing but trouble with kinternet (especially with madwifi (Atheros) wireless). So I switched my boxes to use traditional ifup and have not had a single problem since. If you want to be able to turn it on or off, then you will probably want to keep kinternet (or just issue the ifup/ifdown <interface>). There are several connection options in Yast, on boot, on cable connection, hot plug, etc... You will just have to experiment with the one that will actually let kinternet do what you want it to do. I use 'on boot' because I access a lot of my boxes by ssh and I *always* want the network up regardless of that desktop the user may have up. The yast/network wiki page explains the different connection options (sorry no link), take a look and try the ones that look useful and let us know what works. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2010. október 27. 22:22 napon "David C. Rankin"
On 10/26/2010 03:42 PM, Istvan Gabor wrote:
Hello David,
Thank you for your help. I tried knemo and it works OK, but I would like to be able to turn off and on the network manually. It seems that with knemo I cannot do it. Or can it be configured like that?
Istvan,
knemo just monitors the interface and cannot turn it on or off. I thought you wanted the network 'On' all the time. (that's what I do). That's why I suggested setting the interface to initialize 'on boot'. I have had nothing but trouble with kinternet (especially with madwifi (Atheros) wireless). So I switched my boxes to use traditional ifup and have not had a single problem since.
If you want to be able to turn it on or off, then you will probably want to keep kinternet (or just issue the ifup/ifdown <interface>). There are several connection options in Yast, on boot, on cable connection, hot plug, etc... You will just have to experiment with the one that will actually let kinternet do what you want it to do.
I use 'on boot' because I access a lot of my boxes by ssh and I *always* want the network up regardless of that desktop the user may have up. The yast/network wiki page explains the different connection options (sorry no link), take a look and try the ones that look useful and let us know what works.
Hello David, Thank you again for your help. So far I had no any trouble with kinternet except of that I mentioned, that is it hangs the network connection when the user logs out from his session. I do not use wireless. This only occurs to dsl modedm connection and not to direct network (LAN) connection, I don't know why. I will try the different options in yast as you suggested. Thank you again, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
David C. Rankin -
Istvan Gabor