Bug#416220: network-manager fails to associate with an open (unencrypted) wlan

[Jim Hague]

On Monday 26 March 2007 16:02, Michael Biebl wrote:
> Jim Hague wrote:
> > Package: network-manager
> > Version: 0.6.4-6
> > Severity: normal
> >
> > network-manager on my laptop using the onboard Broadcom BCM4318 via
> > ndiswrapper works fine with WEP and WPA encrypted wireless networks,
> > but fails when connecting to open networks. network-manager-kde shows
> > 28% done 'Activation stage: Configuring device', and sticks there until
> > timing out.
>
> Seems to be a driver issue.
> Your network card driver has to support wext properly for NM to work.

You are quite right. It is definitely a driver issue. I tried a different NDIS 
drivers under x86 and it works properly.

Thanks for your help, and apologies for wasting your time.
-- 
Jim Hague - [EMAIL PROTECTED]  Never trust a computer you can't lift.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#416220: network-manager fails to associate with an open (unencrypted) wlan

[Jim Hague]

On Monday 26 March 2007 16:02, Michael Biebl wrote:
> Jim Hague wrote:
> > Package: network-manager
> > Version: 0.6.4-6
> > Severity: normal
> >
> > network-manager on my laptop using the onboard Broadcom BCM4318 via
> > ndiswrapper works fine with WEP and WPA encrypted wireless networks,
> > but fails when connecting to open networks. network-manager-kde shows
> > 28% done 'Activation stage: Configuring device', and sticks there until
> > timing out.
>
> Seems to be a driver issue.
> Your network card driver has to support wext properly for NM to work.
>
> According to [1], it should be possible to use NM with the native drivers.

Sadly the native drivers don't work with my hardware.

I shall look closer at ndiswrapper, then.
-- 
Jim Hague - [EMAIL PROTECTED]  Never trust a computer you can't lift.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#416220: network-manager fails to associate with an open (unencrypted) wlan

[Michael Biebl]

Jim Hague wrote:
> Package: network-manager
> Version: 0.6.4-6
> Severity: normal
> 
> network-manager on my laptop using the onboard Broadcom BCM4318 via
> ndiswrapper works fine with WEP and WPA encrypted wireless networks,
> but fails when connecting to open networks. network-manager-kde shows
> 28% done 'Activation stage: Configuring device', and sticks there until
> timing out.

Seems to be a driver issue.
Your network card driver has to support wext properly for NM to work.

According to [1], it should be possible to use NM with the native drivers.

Michael


[1] http://live.gnome.org/NetworkManagerHardware

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#416220: network-manager fails to associate with an open (unencrypted) wlan

[Jim Hague]

Package: network-manager
Version: 0.6.4-6
Severity: normal

network-manager on my laptop using the onboard Broadcom BCM4318 via
ndiswrapper works fine with WEP and WPA encrypted wireless networks,
but fails when connecting to open networks. network-manager-kde shows
28% done 'Activation stage: Configuring device', and sticks there until
timing out.

A log of wpa_supplicant traffic follows. Superficially this looks
exactly like Ubuntu bug 42504, 
https://launchpad.net/ubuntu/+source/network-manager/+bug/42504.
The workaround given there, 'sudo dhclient '
works. However, looking at the log it appears that the main problem
there, wpasupplicant being asked to use interface type 'ndiswrapper'
not 'wext', is not the case here.

I am filing this bug from my amd64 install. The x86 install behaves
identically.

Mar 25 23:54:14 scabbers NetworkManager: ^ISUP: sending command 
'INTERFACE_ADD eth1^I^Iwext^I/var/run/wpa_supplicant^I' 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
Global control interface '/var/run/wpa_supplicant-global' 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
RX global ctrl_iface - hexdump_ascii(len=49): 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856):   
   49 4e 54 45 52 46 41 43 45 5f 41 44 44 20 65 74   INTERFACE_ADD et 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856):   
   68 31 09 09 77 65 78 74 09 2f 76 61 72 2f 72 75   h1__wext_/var/ru 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856):   
   6e 2f 77 70 61 5f 73 75 70 70 6c 69 63 61 6e 74   n/wpa_supplicant 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856):   
   09_
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
CTRL_IFACE GLOBAL INTERFACE_ADD 'eth1^I^Iwext^I/var/run/wpa_supplicant^I' 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
Initializing interface 'eth1' conf 'N/A' driver 'wext' ctrl_interface 
'/var/run/wpa_supplicant' bridge 'N/A' 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
Initializing interface (2) 'eth1' 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
EAPOL: SUPP_PAE entering state DISCONNECTED 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
EAPOL: KEY_RX entering state NO_KEY_RECEIVE 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
EAPOL: SUPP_BE entering state INITIALIZE 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
EAP: EAP entering state DISABLED 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
EAPOL: External notification - portEnabled=0 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
EAPOL: External notification - portValid=0 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
SIOCGIWRANGE: WE(compiled)=20 WE(source)=18 enc_capa=0xf 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856):   
capabilities: key_mgmt 0xf enc 0xf 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
WEXT: Operstate: linkmode=1, operstate=5 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): c 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
wpa_driver_wext_set_wpa 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
wpa_driver_wext_set_countermeasures 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
wpa_driver_wext_set_drop_unencrypted 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
Setting scan request: 0 sec 10 usec 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
Added interface eth1 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
Wireless event: cmd=0x8b06 len=12 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP]) 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856): 
RX ctrl_iface - hexdump_ascii(len=9): 
Mar 25 23:54:24 scabbers NetworkManager: ^Iwpa_supplicant(3856):   
   41 50 5f 53 43 41 4e 20 31AP_SCAN 1
Mar 25 23:54:24 scabbers Netw