[opensuse] Wireless Intel 4965AGN
Hi, I installed open suse 10.3 beta 3. After a week I managed to have the wireless working. Yesterday gnome update downloaded heaps of updates (I imagine is because of RC1) and now my wireless just won't work any more. I have it in manual mode as I couldn't manage to make it work with the Network Manager. when I do ifup wlan0 I get the next trace: wlan0 device: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61) wlan0 warning: WPA configured but may be unsupported wlan0 warning: by this device wlan0 starting wpa_supplicant ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 5 value 0x1 - Starting DHCP Client Daemon on wlan0... . . . . . no IP address yet... backgrounding. settings are BOOTPROTO='dhcp' BROADCAST='' ETHTOOL_OPTIONS='' IFPLUGD_PRIORITY='10' IPADDR='' MTU='1500' NAME='Intel WLAN controller' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' WIRELESS_AP='' WIRELESS_AUTH_MODE='psk' WIRELESS_BITRATE='auto' WIRELESS_CA_CERT='' WIRELESS_CHANNEL='' WIRELESS_CLIENT_CERT='' WIRELESS_CLIENT_KEY='' WIRELESS_CLIENT_KEY_PASSWORD='' WIRELESS_DEFAULT_KEY='0' WIRELESS_EAP_AUTH='' WIRELESS_EAP_MODE='' WIRELESS_ESSID='_MI_NETWORK_01_' WIRELESS_FREQUENCY='' WIRELESS_KEY='' WIRELESS_KEY_0='' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_PEAP_VERSION='' WIRELESS_POWER='no' WIRELESS_WPA_ANONID='' WIRELESS_WPA_IDENTITY='' WIRELESS_WPA_PASSWORD='' WIRELESS_WPA_PSK='pskkey' thanks in advance Andres -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 22 September 2007 23:09, Andrés Cosa wrote:
Hi, I installed open suse 10.3 beta 3. After a week I managed to have the wireless working. Yesterday gnome update downloaded heaps of updates
<snip>
WIRELESS_MODE='Managed'
Isn't this stating that you have Network Manager doing your dirty work? IIRC, "managed" means you're not using ifup and ifdown. Or is that 'ad_hoc' setting?
WIRELESS_WPA_PASSWORD='' WIRELESS_WPA_PSK='pskkey'
I wonder if this might be an issue, too? -- kai ponte www.perfectreign.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Kai, I have been using Network Manager to do some changes, but I don't think that is the issue. Before the update it was working perfect. The only thing is that I had to call iwconfig wlan0 essid myessid on startup. But other than that was working ok. After restarting the laptop the first time after the update, the wireless wouldn't work any more (I didn't change anything). Seems to be something with the wpa-psk because now it is working ok with wep. Still want to use wpa-psk. Kai Ponte wrote:
On Saturday 22 September 2007 23:09, Andrés Cosa wrote:
Hi, I installed open suse 10.3 beta 3. After a week I managed to have the wireless working. Yesterday gnome update downloaded heaps of updates
<snip>
WIRELESS_MODE='Managed'
Isn't this stating that you have Network Manager doing your dirty work? IIRC, "managed" means you're not using ifup and ifdown. Or is that 'ad_hoc' setting?
WIRELESS_WPA_PASSWORD='' WIRELESS_WPA_PSK='pskkey'
I wonder if this might be an issue, too?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kai Ponte wrote:
On Saturday 22 September 2007 23:09, Andrés Cosa wrote:
Hi, I installed open suse 10.3 beta 3. After a week I managed to have the wireless working. Yesterday gnome update downloaded heaps of updates
<snip>
WIRELESS_MODE='Managed'
Isn't this stating that you have Network Manager doing your dirty work? IIRC, "managed" means you're not using ifup and ifdown. Or is that 'ad_hoc' setting?
WIRELESS_WPA_PASSWORD='' WIRELESS_WPA_PSK='pskkey'
I wonder if this might be an issue, too?
I dont think WIRELESS_MODE has anything to do with network manager. I think 'Managed' is a synonym for what is called 'Infrastructure' mode. I do not use network manager, and I have these settings. (My experiments with network manager did not impress me with it). WIRELESS_WPA_PSK is correct if pskkey is the ahared key, and the there is nothing wrong with the other setting. These settings are used only if the authorisation mode is set to a mode which requires them (which is kind of handy). The error messages seem to indicate a problem with wpa_supplicant, rather than the device driver, I would ifdown then ifup to test this, a previously broken connection can cause problems. A likely issue is that from some reason wpa_supplicant is either being passed the wrong device info, or is broken for that device, It is also possible the device driver WPA support is broken. I would be a bit worried the device being identified as 'Intel LAN Controller' rather than a specific piece of hardware e.g. "Intel PRO/Wireless 2200BG" (this could suggest use of a generic driver rather than a specific driver). If it is possible I would try and isolate wpa_supplicant as the problem from the device driver. My experience with wpa_supplicant suggests that it can be very twitchy about hardware. I would look a bit more closely at what driver is in use. You may find that you have to create your own load script to get a working configuration. (I do not have your Intel wireless hardware, but I do have intel hardware). In my case I use hwup in a script to initially load my WiFi. (and use ifup, ifdown, ifconfig, iwconfig etc thereafter). The problem was with all these tools to work was that the network device name has to be assigned, and hwup forced the assignment of the device name that was not being assigned on boot which was one of my problems. (9.3 did load OK but before the days of udev I never knew which device name was being associated with which bit of hardware). - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG93WwasN0sSnLmgIRAtDqAJ9nmcDiXhwtdtN2VBmekYXyFv98UgCgsK2M 30gTMmxG5nGbepYT0VPdqSU= =A7zv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ok, My router has an option to disable ssid broadcast. The option was unticked (that is I disabled broadcast in the past). If I enable that option it works fine. I'll try to find out if there is any other option to allow it to work in those conditions (don't recall seeing anyone though). Any ideas? Thanks very much for all the info G T Smith wrote:
Kai Ponte wrote:
On Saturday 22 September 2007 23:09, Andrés Cosa wrote:
Hi, I installed open suse 10.3 beta 3. After a week I managed to have the wireless working. Yesterday gnome update downloaded heaps of updates <snip>
WIRELESS_MODE='Managed' Isn't this stating that you have Network Manager doing your dirty work? IIRC, "managed" means you're not using ifup and ifdown. Or is that 'ad_hoc' setting?
WIRELESS_WPA_PASSWORD='' WIRELESS_WPA_PSK='pskkey' I wonder if this might be an issue, too?
I dont think WIRELESS_MODE has anything to do with network manager. I think 'Managed' is a synonym for what is called 'Infrastructure' mode. I do not use network manager, and I have these settings. (My experiments with network manager did not impress me with it).
WIRELESS_WPA_PSK is correct if pskkey is the ahared key, and the there is nothing wrong with the other setting. These settings are used only if the authorisation mode is set to a mode which requires them (which is kind of handy).
The error messages seem to indicate a problem with wpa_supplicant, rather than the device driver, I would ifdown then ifup to test this, a previously broken connection can cause problems. A likely issue is that from some reason wpa_supplicant is either being passed the wrong device info, or is broken for that device, It is also possible the device driver WPA support is broken. I would be a bit worried the device being identified as 'Intel LAN Controller' rather than a specific piece of hardware e.g. "Intel PRO/Wireless 2200BG" (this could suggest use of a generic driver rather than a specific driver).
If it is possible I would try and isolate wpa_supplicant as the problem from the device driver. My experience with wpa_supplicant suggests that it can be very twitchy about hardware. I would look a bit more closely at what driver is in use.
You may find that you have to create your own load script to get a working configuration. (I do not have your Intel wireless hardware, but I do have intel hardware).
In my case I use hwup in a script to initially load my WiFi. (and use ifup, ifdown, ifconfig, iwconfig etc thereafter). The problem was with all these tools to work was that the network device name has to be assigned, and hwup forced the assignment of the device name that was not being assigned on boot which was one of my problems. (9.3 did load OK but before the days of udev I never knew which device name was being associated with which bit of hardware).
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 24 September 2007 05:23, Andrés Cosa wrote:
Ok,
My router has an option to disable ssid broadcast.
The option was unticked (that is I disabled broadcast in the past). If I enable that option it works fine. I'll try to find out if there is any other option to allow it to work in those conditions (don't recall seeing anyone though). Any ideas?
So, if you DISABLE the SSID you can connect but if you ENABLE it you cannot? That's odd. I usually have my SSID not broadcasting but I've been able to connect either way. (I use Network manager and KDE.) The only issue I had in the past was with my system accidently connecting to my neighbors open access point. However, that was solved by removing them from the preferred list. -- kai ponte www.perfectreign.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
No, the other way round. if I DISABLE the SSID broadcast in the router I cannot connect but if I ENABLE SSID broadcast in the router I can connect. Kai Ponte wrote:
On Monday 24 September 2007 05:23, Andrés Cosa wrote:
Ok,
My router has an option to disable ssid broadcast.
The option was unticked (that is I disabled broadcast in the past). If I enable that option it works fine. I'll try to find out if there is any other option to allow it to work in those conditions (don't recall seeing anyone though). Any ideas?
So, if you DISABLE the SSID you can connect but if you ENABLE it you cannot?
That's odd.
I usually have my SSID not broadcasting but I've been able to connect either way. (I use Network manager and KDE.) The only issue I had in the past was with my system accidently connecting to my neighbors open access point. However, that was solved by removing them from the preferred list.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrés Cosa wrote:
Ok,
My router has an option to disable ssid broadcast.
The option was unticked (that is I disabled broadcast in the past). If I enable that option it works fine. I'll try to find out if there is any other option to allow it to work in those conditions (don't recall seeing anyone though). Any ideas?
Thanks very much for all the info
Hmmm... Under 9.x the SuSE WiFi scripts used the contents of the ifcfg file to generate a temporary wpa_supplicant configuration file and then called wpa_supplicant with the (hopefully) appropriate hardware switch. I have not looked too closely at what is happening under 10.2 but I would expect something similar. wpa_supplicant effectively extends the WiFi API to give support for WPA encryption (WEP support is usually embedded in the driver stack). This rather looks as if the driver in use is not able to initiate a connection to an 'unknown' network, this could indicate that parts of the API relating to WiFi are not functioning. I have had problems where the wireless device has been somehow identified as an ordinary LAN card, but as wpa_supplicant is supplying part of the WiFi support function, one appears to be getting some sort of WiFi connection. I would check whether you have a true WiFi device driver loaded. I would use hwinfo to see what is being loaded... If there is not a specific WiFi driver identified I would look into the possibility of using the Windows drivers with NDISWRAPPER. - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG+MZnasN0sSnLmgIRAhYoAKClYjL9HqoyE3+UAHVnAyJbhRO0TACbBlMr mA2k8SnbqS2BRAOLDPNdUPw= =35VQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Andrés Cosa
-
G T Smith
-
Kai Ponte