I'm trying to get my arms around setting up ifplugd correctly for my environment on an IBM R52 laptop with Intel wireless. The laptop previously dual-booted WinXP and SuSE 10.0 (KDE). I wiped the WinXP partition to install 10.1 (Gnome). I have a need to connect to several wireless locations. In 10.0, I used YaST and ifup/down to configure my connection settings because Kinternet didn't handle WPA-PSK. It was suggested to me I use SCPM to set up location profiles, similar to what IBM's Think Vantage Connections applet does, but I confess I never got around to doing that. 10.1 came configured with ifplug, so I am looking for advice on the best way to have fairly seamless connections. Here are the connection scenarios: I. Office: If I am sitting at my desk, I connect my laptop to the network via Ethernet. If we move to conference room, we use wireless with WPA-PSK. II. Home: Pretty much same as the office. If I sit at a desk with Ethernet, I use it. Elsewhere, I use wireless with WPA-PSK (different ESSID and passphrase than in the office). III. Client Sites and Internet Cafes Typically no encryption. Any suggestions how best to configure the laptop for these uses would be appreciated. Thanks! Mark -- _________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC "We manage your network so you can manage your business" 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678 Web: http://www.rnome.com This email was sent from Reliable Networks of Maine LLC. It may contain information that is privileged and confidential. If you suspect that you were not intended to receive it, please delete it and notify us as soon as possible. Thank you.
On Sun, May 14, 2006 at 09:04:23AM -0400, L. Mark Stone wrote:
I'm trying to get my arms around setting up ifplugd correctly for my environment on an IBM R52 laptop with Intel wireless.
The laptop previously dual-booted WinXP and SuSE 10.0 (KDE). I wiped the WinXP partition to install 10.1 (Gnome).
I have a need to connect to several wireless locations. In 10.0, I used YaST and ifup/down to configure my connection settings because Kinternet didn't handle WPA-PSK. It was suggested to me I use SCPM to set up location profiles, similar to what IBM's Think Vantage Connections applet does, but I confess I never got around to doing that.
10.1 came configured with ifplug, so I am looking for advice on the best way to have fairly seamless connections. Here are the connection scenarios:
I. Office: If I am sitting at my desk, I connect my laptop to the network via Ethernet. If we move to conference room, we use wireless with WPA-PSK.
II. Home: Pretty much same as the office. If I sit at a desk with Ethernet, I use it. Elsewhere, I use wireless with WPA-PSK (different ESSID and passphrase than in the office).
III. Client Sites and Internet Cafes Typically no encryption.
Any suggestions how best to configure the laptop for these uses would be appreciated.
For such cases of multiple profiles we have now NetworkManager... Works seamless for me. ;) Ciao, Marcus
Quoting Marcus Meissner
On Sun, May 14, 2006 at 09:04:23AM -0400, L. Mark Stone wrote:
Any suggestions how best to configure the laptop for these uses would be appreciated.
For such cases of multiple profiles we have now NetworkManager...
Works seamless for me. ;)
There is no Gnome icon on any of the menus for Network Manager. Beagle does not find it. The documentation in /usr/share/doc/packages does not indicate how to configure trusted or preferred wireless access points. The man page for NetworkManager is equally sparse. Can you point me to the documentation for setting up NetworkManager please? Thanks, Mark -- _________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC "We manage your network so you can manage your business" 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678 Web: http://www.rnome.com This email was sent from Reliable Networks of Maine LLC. It may contain information that is privileged and confidential. If you suspect that you were not intended to receive it, please delete it and notify us as soon as possible. Thank you.
On Sun, 2006-05-14 at 09:04 -0400, L. Mark Stone wrote:
I'm trying to get my arms around setting up ifplugd correctly for my environment on an IBM R52 laptop with Intel wireless.
The laptop previously dual-booted WinXP and SuSE 10.0 (KDE). I wiped the WinXP partition to install 10.1 (Gnome).
I have a need to connect to several wireless locations. In 10.0, I used YaST and ifup/down to configure my connection settings because Kinternet didn't handle WPA-PSK. It was suggested to me I use SCPM to set up location profiles, similar to what IBM's Think Vantage Connections applet does, but I confess I never got around to doing that.
10.1 came configured with ifplug, so I am looking for advice on the best way to have fairly seamless connections. Here are the connection scenarios:
I. Office: If I am sitting at my desk, I connect my laptop to the network via Ethernet. If we move to conference room, we use wireless with WPA-PSK.
II. Home: Pretty much same as the office. If I sit at a desk with Ethernet, I use it. Elsewhere, I use wireless with WPA-PSK (different ESSID and passphrase than in the office).
III. Client Sites and Internet Cafes Typically no encryption.
Any suggestions how best to configure the laptop for these uses would be appreciated.
First off, this should have been posted on suse-linux-e. The ifplugd is for hard wired connections not wireless. For wireless try using networkmanager, although it is -very- poor for encrypted connections. If you have an encrypted connection that does -not- broadcast the essid you need to reenter the config every time you try to use the connection or reboot. Even if the essid is broadcast you still need to reenter the wep key. Why is there not a way to save the info? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Sun, 14 May 2006, Kenneth Schneider wrote: [...]
First off, this should have been posted on suse-linux-e. The ifplugd is for hard wired connections not wireless. For wireless try using networkmanager, although it is -very- poor for encrypted connections. If you have an encrypted connection that does -not- broadcast the essid you need to reenter the config every time you try to use the connection or reboot. Even if the essid is broadcast you still need to reenter the wep key. Why is there not a way to save the info?
This is just not true. I'm using both nm-applet and kNetworkmanager (GNOME and KDE NetworkManager frontends) with my WPA2, non-broadcasting wifi network at home and it's working great! The keys are being stored in kWallet or the gnome-keyring. Regards Christoph
On Sun, 2006-05-14 at 16:31 +0200, Christoph Thiel wrote:
On Sun, 14 May 2006, Kenneth Schneider wrote:
[...]
First off, this should have been posted on suse-linux-e. The ifplugd is for hard wired connections not wireless. For wireless try using networkmanager, although it is -very- poor for encrypted connections. If you have an encrypted connection that does -not- broadcast the essid you need to reenter the config every time you try to use the connection or reboot. Even if the essid is broadcast you still need to reenter the wep key. Why is there not a way to save the info?
This is just not true. I'm using both nm-applet and kNetworkmanager (GNOME and KDE NetworkManager frontends) with my WPA2, non-broadcasting wifi network at home and it's working great! The keys are being stored in kWallet or the gnome-keyring.
For those that do not use kWallet it does -not- store the info and requires you to reenter the config each time you boot up. And using kWallet is -not- making it more secure as once the connection is made you can log out and the connection stays for the next person who logs in. Never had this issue with netgo. Maybe I'll go back to that. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Sun, 14 May 2006, Kenneth Schneider wrote:
First off, this should have been posted on suse-linux-e. The ifplugd is for hard wired connections not wireless. For wireless try using networkmanager, although it is -very- poor for encrypted connections. If you have an encrypted connection that does -not- broadcast the essid you need to reenter the config every time you try to use the connection or reboot. Even if the essid is broadcast you still need to reenter the wep key. Why is there not a way to save the info?
This is just not true. I'm using both nm-applet and kNetworkmanager (GNOME and KDE NetworkManager frontends) with my WPA2, non-broadcasting wifi network at home and it's working great! The keys are being stored in kWallet or the gnome-keyring.
For those that do not use kWallet it does -not- store the info and requires you to reenter the config each time you boot up.
So, what's keeping you from using kWallet or gnome-keyring, which both require a passphrase to be unlocked by default.
And using kWallet is -not- making it more secure as once the connection is made you can log out and the connection stays for the next person who logs in. Never had this issue with netgo. Maybe I'll go back to that.
Sorry, but that sounds like an artificial use-case to me. Regards Christoph
On Sun, 2006-05-14 at 16:59 +0200, Christoph Thiel wrote:
On Sun, 14 May 2006, Kenneth Schneider wrote:
First off, this should have been posted on suse-linux-e. The ifplugd is for hard wired connections not wireless. For wireless try using networkmanager, although it is -very- poor for encrypted connections. If you have an encrypted connection that does -not- broadcast the essid you need to reenter the config every time you try to use the connection or reboot. Even if the essid is broadcast you still need to reenter the wep key. Why is there not a way to save the info?
This is just not true. I'm using both nm-applet and kNetworkmanager (GNOME and KDE NetworkManager frontends) with my WPA2, non-broadcasting wifi network at home and it's working great! The keys are being stored in kWallet or the gnome-keyring.
For those that do not use kWallet it does -not- store the info and requires you to reenter the config each time you boot up.
So, what's keeping you from using kWallet or gnome-keyring, which both require a passphrase to be unlocked by default.
Good documentation on how to integrate NetworkManager with Kwallet. Seems to be the weak link with most packages. All it would take is a simple "Would you like to save this information in Kwallet" dialog. And most people that know how seem to be very reluctant to share the knowledge. I don't want to seem picky here but this is the reason most people I talk to -don't- migrate to a linux distro. The lack of this type of integration. But now this has gotten off of the subject. Still plowing along. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
participants (4)
-
Christoph Thiel -
Kenneth Schneider -
L. Mark Stone -
Marcus Meissner