9.2 -> 9.3, lost wireless
I finally got around to updating my laptop from 9.2 to 9.3. And now the wireless doesn't work. Everything seems to be okay, but it won't get an address if in dhcp. Will let me set a static ip, but won't even ping the router. I did an online update via wire last night, no joy. This is a built in wireless b in a 2 yr old toshiba laptop. It's been working in 9.1 and 9.2. Shows up as an Intersil Prism or something like that. Can anyone give me some troubleshooting ideas? Thanks, Joe
I had a very similar problem with a Dell laptop with a Prism card. Turned out the default for the "wireless authentication mode" had changed from "shared" to "open". To fix this, I added WIRELESS_AUTH_MODE='shared' to the ifcfg-file corresponding to my wlan card. (In my case, /etc/sysconfig/network/ifcfg-wlan-bus-pcmcia) After a network restart, my laptop connected OK. /Lennart måndagen den 17 oktober 2005 14.59 skrev Joe Georger:
I finally got around to updating my laptop from 9.2 to 9.3. And now the wireless doesn't work. Everything seems to be okay, but it won't get an address if in dhcp. Will let me set a static ip, but won't even ping the router. I did an online update via wire last night, no joy.
This is a built in wireless b in a 2 yr old toshiba laptop. It's been working in 9.1 and 9.2. Shows up as an Intersil Prism or something like that. Can anyone give me some troubleshooting ideas?
Thanks, Joe
-- !++ ! Lennart Börjeson ! Partner, Developer ! Cinnober Financial Technology AB ! Industrigatan 2A ! S-112 46 STOCKHOLM ! Sverige/Sweden/Schweden/Suède ! mailto:Lennart.Borjeson@cinnober.com ! phone:+46-8-50304717 ! gsm:+46-70-3394717 ! fax:+46-8-50304701 ! http://www.cinnober.com !--
I think my corresponding entry is 'sharedkey'. One other thing that happened in the upgrade - is the the filename changed from something like ifcfg-wlan-bus-pcmcia to ifcfg-wlan-<mac address>.... The wireless didn't initially work. So I went into Yast->network devices and I had a new Toshiba wlan card in the top and the old one already configured. So I deleted the original and configured the new one. I just figured 9.3 addressed the pcmcia wlan card differently than 9.2. Made no difference as the new ifcfg does not work either. Thanks, Joe Lennart Börjeson wrote:
I had a very similar problem with a Dell laptop with a Prism card. Turned out the default for the "wireless authentication mode" had changed from "shared" to "open". To fix this, I added
WIRELESS_AUTH_MODE='shared'
to the ifcfg-file corresponding to my wlan card.
(In my case, /etc/sysconfig/network/ifcfg-wlan-bus-pcmcia)
After a network restart, my laptop connected OK.
/Lennart
måndagen den 17 oktober 2005 14.59 skrev Joe Georger:
I finally got around to updating my laptop from 9.2 to 9.3. And now the wireless doesn't work. Everything seems to be okay, but it won't get an address if in dhcp. Will let me set a static ip, but won't even ping the router. I did an online update via wire last night, no joy.
This is a built in wireless b in a 2 yr old toshiba laptop. It's been working in 9.1 and 9.2. Shows up as an Intersil Prism or something like that. Can anyone give me some troubleshooting ideas?
Thanks, Joe
If you inspect the wlan settings with iwconfig, do they look alright? If I remember correctly, one indication for my problem was that the hardware address of the AP was reported as 44:44:44:44:44:44:44. A bogus value, but this indicated that the wlan card had connected but was refused access. But this was propably only true for certain versions of the orinoco driver, so it may or may not apply to your system. /Lennart måndagen den 17 oktober 2005 15.59 skrev Joe Georger:
I think my corresponding entry is 'sharedkey'.
One other thing that happened in the upgrade - is the the filename changed from something like
ifcfg-wlan-bus-pcmcia
to
ifcfg-wlan-<mac address>....
The wireless didn't initially work. So I went into Yast->network devices and I had a new Toshiba wlan card in the top and the old one already configured. So I deleted the original and configured the new one. I just figured 9.3 addressed the pcmcia wlan card differently than 9.2. Made no difference as the new ifcfg does not work either.
Thanks, Joe
Lennart Börjeson wrote:
I had a very similar problem with a Dell laptop with a Prism card. Turned out the default for the "wireless authentication mode" had changed from "shared" to "open". To fix this, I added
WIRELESS_AUTH_MODE='shared'
to the ifcfg-file corresponding to my wlan card.
(In my case, /etc/sysconfig/network/ifcfg-wlan-bus-pcmcia)
After a network restart, my laptop connected OK.
/Lennart
måndagen den 17 oktober 2005 14.59 skrev Joe Georger:
I finally got around to updating my laptop from 9.2 to 9.3. And now the wireless doesn't work. Everything seems to be okay, but it won't get an address if in dhcp. Will let me set a static ip, but won't even ping the router. I did an online update via wire last night, no joy.
This is a built in wireless b in a 2 yr old toshiba laptop. It's been working in 9.1 and 9.2. Shows up as an Intersil Prism or something like that. Can anyone give me some troubleshooting ideas?
Thanks, Joe
-- !++ ! Lennart Börjeson ! Partner, Developer ! Cinnober Financial Technology AB ! Industrigatan 2A ! S-112 46 STOCKHOLM ! Sverige/Sweden/Schweden/Suède ! mailto:Lennart.Borjeson@cinnober.com ! phone:+46-8-50304717 ! gsm:+46-70-3394717 ! fax:+46-8-50304701 ! http://www.cinnober.com !--
I'm not familiar with any wireless command line utils.... I'll have to check that when I get home from work. You know, now that I think about it, even running 9.2 I could not connect to say an airport wifi hotspot. In kwifimanager, I would get a signal but could never get an ip, even after reconfiguring my card in yast to use open authentication. I think in kwifimanager I would get the AP as some bogus value like you mentioned. What is going on there? This was one of my primary reasons for upgrading. Now I bet it is happening to my home network.... Thanks, Joe Lennart Börjeson wrote:
If you inspect the wlan settings with iwconfig, do they look alright?
If I remember correctly, one indication for my problem was that the hardware address of the AP was reported as 44:44:44:44:44:44:44. A bogus value, but this indicated that the wlan card had connected but was refused access.
But this was propably only true for certain versions of the orinoco driver, so it may or may not apply to your system.
/Lennart
måndagen den 17 oktober 2005 15.59 skrev Joe Georger:
I think my corresponding entry is 'sharedkey'.
One other thing that happened in the upgrade - is the the filename changed from something like
ifcfg-wlan-bus-pcmcia
to
ifcfg-wlan-<mac address>....
The wireless didn't initially work. So I went into Yast->network devices and I had a new Toshiba wlan card in the top and the old one already configured. So I deleted the original and configured the new one. I just figured 9.3 addressed the pcmcia wlan card differently than 9.2. Made no difference as the new ifcfg does not work either.
Thanks, Joe
Lennart Börjeson wrote:
I had a very similar problem with a Dell laptop with a Prism card. Turned out the default for the "wireless authentication mode" had changed from "shared" to "open". To fix this, I added
WIRELESS_AUTH_MODE='shared'
to the ifcfg-file corresponding to my wlan card.
(In my case, /etc/sysconfig/network/ifcfg-wlan-bus-pcmcia)
After a network restart, my laptop connected OK.
/Lennart
måndagen den 17 oktober 2005 14.59 skrev Joe Georger:
I finally got around to updating my laptop from 9.2 to 9.3. And now the wireless doesn't work. Everything seems to be okay, but it won't get an address if in dhcp. Will let me set a static ip, but won't even ping the router. I did an online update via wire last night, no joy.
This is a built in wireless b in a 2 yr old toshiba laptop. It's been working in 9.1 and 9.2. Shows up as an Intersil Prism or something like that. Can anyone give me some troubleshooting ideas?
Thanks, Joe
Do a iwconfig wlan0 as root and check the output. You should see your ESSID, the address of your AP etc. The Security mode should be "restricted". Your key should be there, etc etc. You should also be able to try out different settings from the command line; sometimes faster to do it that way and then finalise everything in yast. /Lennart måndagen den 17 oktober 2005 16.33 skrev Joe Georger:
I'm not familiar with any wireless command line utils.... I'll have to check that when I get home from work. You know, now that I think about it, even running 9.2 I could not connect to say an airport wifi hotspot. In kwifimanager, I would get a signal but could never get an ip, even after reconfiguring my card in yast to use open authentication. I think in kwifimanager I would get the AP as some bogus value like you mentioned. What is going on there? This was one of my primary reasons for upgrading. Now I bet it is happening to my home network....
Thanks, Joe
Lennart Börjeson wrote:
If you inspect the wlan settings with iwconfig, do they look alright?
If I remember correctly, one indication for my problem was that the hardware address of the AP was reported as 44:44:44:44:44:44:44. A bogus value, but this indicated that the wlan card had connected but was refused access.
But this was propably only true for certain versions of the orinoco driver, so it may or may not apply to your system.
/Lennart
måndagen den 17 oktober 2005 15.59 skrev Joe Georger:
I think my corresponding entry is 'sharedkey'.
One other thing that happened in the upgrade - is the the filename changed from something like
ifcfg-wlan-bus-pcmcia
to
ifcfg-wlan-<mac address>....
The wireless didn't initially work. So I went into Yast->network devices and I had a new Toshiba wlan card in the top and the old one already configured. So I deleted the original and configured the new one. I just figured 9.3 addressed the pcmcia wlan card differently than 9.2. Made no difference as the new ifcfg does not work either.
Thanks, Joe
Lennart Börjeson wrote:
I had a very similar problem with a Dell laptop with a Prism card. Turned out the default for the "wireless authentication mode" had changed from "shared" to "open". To fix this, I added
WIRELESS_AUTH_MODE='shared'
to the ifcfg-file corresponding to my wlan card.
(In my case, /etc/sysconfig/network/ifcfg-wlan-bus-pcmcia)
After a network restart, my laptop connected OK.
/Lennart
måndagen den 17 oktober 2005 14.59 skrev Joe Georger:
I finally got around to updating my laptop from 9.2 to 9.3. And now the wireless doesn't work. Everything seems to be okay, but it won't get an address if in dhcp. Will let me set a static ip, but won't even ping the router. I did an online update via wire last night, no joy.
This is a built in wireless b in a 2 yr old toshiba laptop. It's been working in 9.1 and 9.2. Shows up as an Intersil Prism or something like that. Can anyone give me some troubleshooting ideas?
Thanks, Joe
-- !++ ! Lennart Börjeson ! Partner, Developer ! Cinnober Financial Technology AB ! Industrigatan 2A ! S-112 46 STOCKHOLM ! Sverige/Sweden/Schweden/Suède ! mailto:Lennart.Borjeson@cinnober.com ! phone:+46-8-50304717 ! gsm:+46-70-3394717 ! fax:+46-8-50304701 ! http://www.cinnober.com !--
Strange. The output of iwconfig showed no ssid, open authentication, and no key. If I set them manually the wireless would work. However upon reboot it was back to not working. Now this is with those same parameters set in the ifcfg file.... I spent about an hour searching the SLE archives and came up with one message saying to add this to my ifcfg file: HWD_INTERFACETYPE_0=wlan I did that and it worked! But what the hell? Joe Lennart Börjeson wrote:
Do a
iwconfig wlan0
as root and check the output. You should see your ESSID, the address of your AP etc. The Security mode should be "restricted". Your key should be there, etc etc. You should also be able to try out different settings from the command line; sometimes faster to do it that way and then finalise everything in yast.
/Lennart
Strange indeed. I really don't know much about it, but the HWD_* parameters are somehow built and returned by the "getcfg" utility which "ifup" uses. I'm gussing getcfg does not (by reasons unknown) understand that your card is wireless. It should also do this if you set WIRELESS=yes in your ifcfg-file. But I'm just guessing. Good that you've found a way around the problem, anyway. /Lennart tisdagen den 18 oktober 2005 14.14 skrev Joe Georger:
Strange. The output of iwconfig showed no ssid, open authentication, and no key. If I set them manually the wireless would work. However upon reboot it was back to not working. Now this is with those same parameters set in the ifcfg file....
I spent about an hour searching the SLE archives and came up with one message saying to add this to my ifcfg file:
HWD_INTERFACETYPE_0=wlan
I did that and it worked! But what the hell?
Joe
Lennart Börjeson wrote:
Do a
iwconfig wlan0
as root and check the output. You should see your ESSID, the address of your AP etc. The Security mode should be "restricted". Your key should be there, etc etc. You should also be able to try out different settings from the command line; sometimes faster to do it that way and then finalise everything in yast.
/Lennart
-- !++ ! Lennart Börjeson ! Partner, Developer ! Cinnober Financial Technology AB ! Industrigatan 2A ! S-112 46 STOCKHOLM ! Sverige/Sweden/Schweden/Suède ! mailto:Lennart.Borjeson@cinnober.com ! phone:+46-8-50304717 ! gsm:+46-70-3394717 ! fax:+46-8-50304701 ! http://www.cinnober.com !--
participants (2)
-
Joe Georger -
Lennart Börjeson