WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: iw, libnl and wpa_supplicant  (Read 5343 times)

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14798
iw, libnl and wpa_supplicant
« on: April 13, 2013, 02:26:13 AM »
As I'm looking into the cfg80211 wireless interface, it would useful to have the latest versions of iw, libnl and wpa_supplicant to avoid possible sources of errors.

Offline gutmensch

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 605
  • I can make it disappear, have no fear!
    • remembrance blog
Re: iw, libnl and wpa_supplicant
« Reply #1 on: April 14, 2013, 05:50:31 AM »
Just uploaded latest libnl (3.2.21) and wpa_supplicant (2.0)!
If I seem unduly clear to you, you must have misunderstood what I said. (Alan Greenspan)

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14798
Re: iw, libnl and wpa_supplicant
« Reply #2 on: April 14, 2013, 05:54:31 AM »
Thanks  :)

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14798
Re: iw, libnl and wpa_supplicant
« Reply #3 on: April 14, 2013, 06:35:52 AM »
.and now there are no more error messages:
Code: [Select]
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
cfg80211: Calling CRDA to update world regulatory domain
wl 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
wl 0000:02:00.0: setting latency timer to 64
INFO @wl_cfg80211_attach : Registered CFG80211 phy
lib80211_crypt: registered algorithm 'TKIP'
eth1: Broadcom BCM4359 802.11 Hybrid Wireless Controller 5.100.82.112

I'll post the new wl-modules-KERNEL in due course

Offline gutmensch

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 605
  • I can make it disappear, have no fear!
    • remembrance blog
Re: iw, libnl and wpa_supplicant
« Reply #4 on: April 14, 2013, 06:47:43 AM »
nice work! :)
If I seem unduly clear to you, you must have misunderstood what I said. (Alan Greenspan)

Offline bobert3316

  • Newbie
  • *
  • Posts: 11
Re: iw, libnl and wpa_supplicant
« Reply #5 on: April 26, 2013, 04:02:20 PM »
Just uploaded latest libnl (3.2.21) and wpa_supplicant (2.0)!

Could you please post the .config that you used to build wpa_supplicant?  Was bgscan enabled?  If not, I'll need to build my own copy that has it enabled, and I'd like to start with your .config. 

Thanks!

Offline gutmensch

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 605
  • I can make it disappear, have no fear!
    • remembrance blog
Re: iw, libnl and wpa_supplicant
« Reply #6 on: April 26, 2013, 04:43:50 PM »
In my tests with 0.7.x the BGSCAN feature caused some kind of stability issues (maybe more related to shitty third party drivers, but well... what can you do), that's why I had it disabled again. But since we are now at 2.0 it might be worth another look. I built with the following config (as can be seen in http://repo.tinycorelinux.net/4.x/x86/tcz/src/wpa_supplicant/wpa_supplicant.build), although I am stripping afterwards, so you might want to remove the -g3 and -DDEBUG switches for size.

Code: [Select]
CONFIG_BACKEND=file
CONFIG_CTRL_IFACE=y
CONFIG_DRIVER_NL80211=y
CONFIG_DRIVER_WEXT=y
CONFIG_DRIVER_WIRED=y
CONFIG_EAP_GTC=y
CONFIG_EAP_LEAP=y
CONFIG_EAP_MD5=y
CONFIG_EAP_MSCHAPV2=y
CONFIG_EAP_OTP=y
CONFIG_EAP_PEAP=y
CONFIG_EAP_TLS=y
CONFIG_EAP_TTLS=y
CONFIG_IEEE8021X_EAPOL=y
CONFIG_LIBNL32=y
CONFIG_PEERKEY=y
CONFIG_PKCS12=y                                                                                       
CONFIG_SMARTCARD=y
CONFIG_WPS=y
CFLAGS += -I/usr/local/include/libnl3
CFLAGS += -march=i486 -mtune=i686 -Os -pipe -fomit-frame-pointer -g3 -DDEBUG
CXXFLAGS += -march=i486 -mtune=i686 -Os -pipe -g3 -DDEBUG
LDFLAGS += -L/usr/local/lib -L/usr/lib -L/lib -Wl,-O1 -Wl,--hash-style=gnu
If I seem unduly clear to you, you must have misunderstood what I said. (Alan Greenspan)

Offline bobert3316

  • Newbie
  • *
  • Posts: 11
Re: iw, libnl and wpa_supplicant
« Reply #7 on: May 28, 2013, 11:52:50 AM »
I've experienced the same result with the latest wpa_supplicant and ralink 3572 drivers from the 3.8 compat-drivers release.  When I set bgscan in the config, it drops the connection after a few minutes to several hours.  When I comment out bgscan in the config, it stays connected, but roams poorly.  Looks like I'm sticking with ralink's proprietary driver for now.  Thanks!