Switching between Ethernet card and Wireless
Dennis J. Tuchler
connection, which is the one that "works" on boot up? How do I switch
between them?
dj tuchler
Alvin
I did exactly this about a month or two ago. Go into Yast and setup
Profiles. A profile is just a snapshot of particular configuration files
like network settings, X settings, etc.
I have 3 profiles:
nonet - Ethernet and Wifi set to manual
wired - Ethernet set to activate at boot. Wifi set to manual
wifi - Ethernet set to manual. Wifi set to activate at boot
What I did, in a nut shell, was:
1. Configure the system (using yast) with ethernet and wifi set to manual.
2. In yast create a new profile and call it 'nonet'
3. Configure the system (using yast) to use ethernet at boot and wifi set to
manual
4. In yast create a new profile and call it 'wired'
5. Configure the system (using yast) to use ethernet manually and wifi at
boot.
6. In yast create a new profile and call it 'wifi'
Then, when you power on you will have an option in grub boot menu that
allows you to select the profile you want. Just press F3 to see the
choices.
There is also a new icon in the system tray that allows you to switch
profiles while logged in.
I would recommend reading the section on Profiles in the Admin section of
the SUSE Help first though.
Enjoy,
Alvin
Dennis J. Tuchler
Thank you for the quick response! It looks simple enough for me to do it.
How/where did you find how to do this?
dj tuchler
Alvin
> How/where did you find how to do this?
I asked a same question. :)
Alvin
ji...@budet.net
myself. That being said, I thought that I would share what I'm
currently doing.
I'm using Suse 9.3 and have eth0 (hardwired) and wlan0 (wifi). Both are
setup to activate at boot time. I'm also using the KInternet tool in
the System Tray.
If I boot with the computer connected to a hardwired network, then that
connection gets an IP address and I'm set. If I boot without a cable,
eth0 fails to get an IP address. At this point I'll right click on the
KIntenet aplet and change my interface from eth0 to wlan0. This will
activate wlan0 using the parameters that I specified for the interface
through Yast. For me, this gets me going on my home wireless network.
If I'm someplace with public wifi, I'll right click on KInternet and
select Wireless Connection... This let's me sniff for access points and
connect to them. It's pretty cool.
I do occassionally run into problems so it's good to get familiar with
the "ifup" and "ifdown" commands. For instance, if I think that the
system is confused and I want it to use eth0, I'll use the commands;
ifdown eth0
ifdown wlan0
ifup eth0
This seems to get the right adapters going with an IP address and get
the routes straight. I hope that this information will be useful to you.
ji...@budet.net
connection, not at boot time.
--JB
houghi
> Using profiles sounds like a good approach and I should look into it
> myself. That being said, I thought that I would share what I'm
> currently doing.
Please read http://www.safalra.com/special/googlegroupsreply/
--
houghi Please do not toppost http://houghi.org
You are about to enter another dimension, a dimension not only of
sight and sound but of mind. A journey into a wondrous land of
imagination. Next stop, Usenet
Alvin
> I'm using Suse 9.3 and have eth0 (hardwired) and wlan0 (wifi). Both are
> setup to activate at boot time. I'm also using the KInternet tool in
> the System Tray.
This is how I originally had my setup as well. But I found that the routing
table wouldn't be properly setup. What would happen is that when I was
wifi, the eth0 would not get an address but the wifi would. However, for
some strange reason the routing table wouldn't have a default (0.0.0.0)
entry.
My solution was to use the profiles and select (at boot) what I was. Or if I
missed the grub screen, or was booting from a suspend-to-disk, I would just
click on the system tray icon.
Alvin