Bugzilla – Bug 585802
switch nl80211 wpa_supplicant driver in ifup-wireless for WIRELESS_REGULATORY_DOMAIN support
Last modified: 2016-04-15 10:52:47 UTC
+++ This bug was initially created as a clone of Bug #537708 +++ Until openSUSE:11.2, we were using the "wext" wpa driver by default. For openSUSE:11.3 it would be required to switch as many drivers as possible to the new "nl80211" driver to not to restricts any devices to "world" (ie. most restrictive) regulatory domain. As already proposed in bug 537708 comment 6, it makes sense to use the new driver as default, except in cases where it does not work. The intention of this bug is to track these non-working cases. See also bug 535750 comment 7: "[...] If the wpa_supplicant is running with the -Dnl80211 then it does not authenticate. -Dwext works fine.[...]" See also bug 555850, crda -- Database signature verification failed.
I'd say it is an important enhancement, not major: the user can set the WIRELESS_WPA_DRIVER='nl80211' variable ...
Tested on _11.2_ final with: * ath5k: Netgear WG511T, PCMCIA Vendor: pci 0x168c "Atheros Communications Inc." Device: pci 0x0013 "Atheros AR5001X+ Wireless Network Adapter" SubVendor: pci 0x1385 "Netgear" SubDevice: pci 0x5b00 Driver: "ath5k" => nl80211 works fine * iwlagn: On-Board wlan of a Dell Latitude E6500 Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x4232 "Wireless WiFi Link 5100" SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x1321 "Wireless WiFi Link 5100" Driver: "iwlagn" => nl80211 works fine, even I get an error message: Failed to set interface wlan0 mode Could not configure driver to use managed mode Vladimir, could you retest bug 535750 comment 7?
btw: what about networkmanager, shouldn't that switch as well ?
(In reply to comment #3) > btw: what about networkmanager, shouldn't that switch as well ? IMO yes -- there is also a feature request for NM. I don't know the details.
Created attachment 348671 [details] let NM set the wpa driver from environment
Maybe the attached patch for Networkmanager will do the trick?
(In reply to comment #6) > Maybe the attached patch for Networkmanager will do the trick? No. This bug is about sysconfig, not really about NM. There is nobody, that could/would set any variable for NM. NM does not read any ifcfg files and this variable is not set by default. => NM has to decide itself how to deal with this issue. In sysconfig this variable is a workaround for cases, when the user wants to change the default (workaround for 11.2 for use nl80211). I'll apply a patch for 11.3 that sets the nl80211 by default and the user can override it with the old 'wext' using WIRELESS_WPA_DRIVER, when nl80211 does not work for him and report a bug about...
(In reply to comment #7) > (In reply to comment #6) > > Maybe the attached patch for Networkmanager will do the trick? > > No. This bug is about sysconfig, not really about NM. There is nobody, > that could/would set any variable for NM. NM does not read any ifcfg > files and this variable is not set by default. NM is started from /etc/inid.d/network script, which reads the file /etc/sysconfig/network/config One could check for the existence of WIRELESS_WPA_DRIVER over there and export it before starting NM like this. [[ "x$WIRELESS_WPA_DRIVER" != "x" ]] && export WIRELESS_WPA_DRIVER $FAKE startproc $NETWORKMANAGER_BIN > => NM has to decide itself how to deal with this issue. NM has "wext" simply hardcoded, it makes no decision at all.
Then it has to be fixed and make the decision somehow. Please open a new bug report for NM and don't mix NM and ifup. (In reply to comment #8) > > NM is started from /etc/inid.d/network script, which reads the file > /etc/sysconfig/network/config The network script starts it but it does not and will not export sysconfig settings to NM. NM is not using any sysconfig settings and we do not plan to change it - please do not mix NM and ifup. > > => NM has to decide itself how to deal with this issue. > > NM has "wext" simply hardcoded, it makes no decision at all. Then I guess it has to be fixed -- please open a new bug report.
(In reply to comment #9) > Then it has to be fixed and make the decision somehow. Please > open a new bug report for NM and don't mix NM and ifup. I have opened bug 591959.
Don't know if this my experience is this bug: Since Milestone6 factory I cannot start wireless through traditional ifup: Something like: "missing netlink module nl80211" Changing back to NetworkManager (using yast2) : wireless connects without problem
(In reply to comment #11) > Don't know if this my experience is this bug: > Since Milestone6 factory I cannot start wireless through traditional ifup: > Something like: "missing netlink module nl80211" The message says that the wlan driver is not able to use the new nl80211 extension yet. You can use the old wext extension. Set WIRELESS_WPA_DRIVER="wext" in /etc/sysconfig/network/config. What wlan driver and wlan adapter do you use ? Could you post hwinfo --wlan ? Does setting wext work for you ?
Did find myself: "wext" for broadcom-sta-kmp-desktop home:/computersalat:/KMP:/Update/openSUSE_Factory/ ...also kernel-module nl80211.ko doesn't exist, which I searched for in the first place, but it is built-in compiled.
home:/computersalat:/KMP:/Update/openSUSE_Factory/ provides wl driver which works setting: WIRELESS_WPA_DRIVER="wext" in /etc/sysconfig/network/config --- hwinfo --wlan --- 21: PCI 300.0: 0282 WLAN controller [Created at pci.318] Unique ID: JNkJ.p5UqXEvSxE1 Parent ID: Rgik.RRGuB29h369 SysFS ID: /devices/pci0000:00/0000:00:15.0/0000:03:00.0 SysFS BusID: 0000:03:00.0 Hardware Class: network Model: "Broadcom BCM4328 802.11a/b/g/n" Vendor: pci 0x14e4 "Broadcom" Device: pci 0x4328 "BCM4328 802.11a/b/g/n" SubVendor: pci 0x106b "Apple Computer Inc." SubDevice: pci 0x0090 Revision: 0x05 Driver: "wl" Driver Modules: "wl" Device File: eth1 Features: WLAN Memory Range: 0xd3200000-0xd3203fff (rw,non-prefetchable) IRQ: 23 (no events) HW Address: 00:26:08:ed:96:26 Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7 WLAN bitrates: 1 2 5.5 6 9 11 12 18 24 36 48 54 WLAN encryption modes: WEP40 WEP104 WEP256 WEP128 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v000014E4d00004328sv0000106Bsd00000090bc02sc80i00" Driver Info #0: Driver Status: ssb is not active Driver Activation Cmd: "modprobe ssb" Driver Info #1: Driver Status: wl is active Driver Activation Cmd: "modprobe wl" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #18 (PCI bridge)
SRID 40602 wl driver from broadcom shall use wext
(In reply to comment #15) > SRID 40602 > wl driver from broadcom shall use wext Thanks! Applied your patch from sr 40602 to git, then to Base:System/sysconfig. Goes to factory via sr #40636. (In reply to comment #14) > home:/computersalat:/KMP:/Update/openSUSE_Factory/ provides wl driver which > works setting: > WIRELESS_WPA_DRIVER="wext" in /etc/sysconfig/network/config Thanks Ralph! BTW: ifcfg-eth1 would be sufficient here.
bug 555850 is for 11.2, not 11.3.
factory is using the new driver already a while => fixed.
This is an autogenerated message for OBS integration: This bug (585802) was mentioned in https://build.opensuse.org/request/show/40636 Factory / sysconfig