Bug 158892

Created attachment 73440 [details]
/var/log/NetworkManager log

What card are you using ndiswrapper on?

It is a BCM4318 "Air Force One 54G"

hwinfo --netcard

26: PCI 303.0: 0280 Network controller
  [Created at pci.295]
  UDI: /org/freedesktop/Hal/devices/pci_14e4_4318
  Unique ID: y9sn.GzN3dC+wUS1
  Parent ID: 6NW+.InKz0bgid89
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:03:03.0
  SysFS BusID: 0000:03:03.0
  Hardware Class: network
  Model: "Dell BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller"
  Vendor: pci 0x14e4 "Broadcom"
  Device: pci 0x4318 "BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller                                                           "
  SubVendor: pci 0x1028 "Dell"
  SubDevice: pci 0x0005
  Revision: 0x02
  Driver: "ndiswrapper"
  Device File: wlan0
  Features: WLAN
  Memory Range: 0xdfcfe000-0xdfcfffff (rw,non-prefetchable)
  IRQ: 201 (733824 events)
  HW Address: 00:16:ce:19:85:39
  Link detected: yes
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
  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 2.484
  WLAN bitrates: 6 9 12 18 18.5 18.5
  WLAN encryption modes: WEP40 WEP104
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Module Alias: "pci:v000014E4d00004318sv00001028sd00000005bc02sc80i00"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #16 (PCI bridge)

Is the AP that you are attempting to connect to broadcasting?  Is it an Ad-Hoc network or a normal one?

I doubt this is an applet bug, but are you using KNM or nm-applet?

The log file on Comment#1 shows that I tried to connect to 2 APs (Graphics 270 and KMC224) I know for sure KMC224 is working on "Managed" or normal mode, the other I don't know. I tried to connect to my router at home and to the public wireless network at school (I'm pretty sure both using "managed" mode) with the same results. If you need me to attach the /var/log/NetworkManager from both APs (home and school) I could.

I'm using KNM 

Sorry from previous comment I meant to say :
If you need me to attach the /var/log/NetworkManager showing the log when I tried to connect to both APs (home and school) I could.

Something I think it is weired I found on the log file is that it "times out" authenticating with 00:00:00:00:00:00

---------
selected non-WPA AP 00:06:25:c0:77:15 ssid='101KMC'
<information>	wpa_supplicant(8668): Trying to associate with 00:06:25:c0:77:15 (SSID='101KMC' freq=2437 MHz)
<information>	wpa_supplicant(8668): CTRL_IFACE monitor send - hexdump(len=42): 2f 76 61 72 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 38 33 30 32 2d 33 00 30 00
...
<information>	wpa_supplicant(8668): State: SCANNING -> ASSOCIATING
<information>	wpa_supplicant(8668): Setting authentication timeout: 10 sec 0 usec
<information>	wpa_supplicant(8668): EAPOL: External notification - portControl=ForceAuthorized
<information>	wpa_supplicant(8668): Authentication with 00:00:00:00:00:00 timed out
-------------

I don't know if that has something to do with the problem

In Beta 3 NetworkManager worked with ndiswrapper (but not modems).  In Beta 8, modems work but not networkmanager.  I'm following bug #153243 and the current changes are to increase the delay for dhcp.  This has not worked for me or a co-worker.  Using wificonfig (sourceforge) works for both of us and connects in less than 5 secounds.  

It appears that updates put in since Beta 3 to fix other problems maybe causing the problems that testers are seeing with wireless now.

*** Bug 156399 has been marked as a duplicate of this bug. ***

Created attachment 75182 [details]
/var/log/NetworkManager

This is my NetworkManager log.  The NDIS driver used is bcmwl5a.

There have been changes made to the 1.12 and 1.13rc versions of ndiswrapper.  These changes allow it to respond to wpa calling it via wext.  However, the current Networkmanager/wpa still use ndiswrapper as the driver name.  At this time, I can connect to encrypted AP's but not unencypted AP's. 

*** Bug 164527 has been marked as a duplicate of this bug. ***

So, unfortunately we are not shipping 1.13, but 1.10.  So we do not have those fixes.  jg is looking into back-porting them.  If so, I'll switch our package to the wext driver.

It looks like 1.12 added support for WEP with the wext driver.  And 1.13 added support for non-encrypted networks (1.12 may have broken them?).

Right now, with our 1.10 package, WEP does not work with the wext driver.

I just upgraded my ndiswrapper to 1.13 and that didn't seem to help at all. Same problem with the same symptoms:

 # ndiswrapper -v
utils version: 1.8
driver version:        1.13
vermagic:       2.6.16-8-smp SMP 586 REGPARM gcc-4.1

Is there something else I should change as well other than just upgrade ndiswrapper?

Yes, you would need to modify NetworkManager to not use the ndiswrapper driver, but use the wext driver, instead.

If you get the source RPM, this would be easy: Edit nm-wireless-workarounds.patch and remove the if that checks for and changes behavior in response to ndiswrapper and then rebuild.

Alternatively, you could use the ndiswrapper package of mbuild job angua-jg-1 and NetworkManager package of angua-jg-2. The ndiswrapper package is still a 1.10 version, but with a backported fix. But you probably need a newer kernel package and maybe some packages NM depends on, too (e.g. dbus-1).

The patch is rather small and simple, I don't think it will break something. I've successfully connected to networks with no encryption, WEP, and WPA-PSK (all both hidden and visible) with it, so it looks quite good to me.

Andreas, is it possible to get that into 10.1? Short summarisation: the ndiswrapper patch together with NetworkManager patch from 165315 should give us full ndiswrapper support. Currently we lack support for non-encrypted networks and hidden networks.

Indeed.. if we could work that in it would be much appreciated.. As of now I have to manually ifup to connect to a hidden network and then to use vpn with that is a bit of a pain... having it all included in the network manager would be optimal. Joachim.. where can I find the packages that you are referring to?

ndiswrapper package of mbuild job angua-jg-1
and NetworkManager package of angua-jg-2

Joe, please submit directly so this can go in for RC2.

Ok, submitted ndiswrapper and NetworkManager.

Jake, I guess you need access to SUSE autobuild to grab these packages. If you don't have, I could send you them, but as you most probably need other packages too, this may get quite long-winded. Could you try with RC2, as soon as available?

I'll do so too once RC2 hits the servers.

*** Bug 165207 has been marked as a duplicate of this bug. ***

*** Bug 164394 has been marked as a duplicate of this bug. ***

jg: Sie sind ein Gott unter Männern.

Did you update STABLE too, for SLES/SLED 10?  If not, I will happily update the NM bits.

I'll wait for RC2 and hope for the best.. Thanks for the quick reply Joachim. When do we expect RC2 to be out?... April 19th ish?

Comment 24: I can't tell. However, the packages I've built should work with RC1, so you could also test it with RC1, if you want.

Comment 23: Package was checked into STABLE, and after RC1 is final the autobuild team will check it into 10.1 as well, I guess. Oh, and you may address me with "Du", really. :-)

jg: Excellent.  Bug should be fixed, then!

Closing as per comments.

I still could not connect to open AP with 10.1 RC1 with ndiswrapper.  Encrypted AP's were no problem.  This is in 64 bit and I tested a athros based card using madwifi.  Madwifi would connect to open or encrypted networks here at work.  Networkmanager uses apscan=1 for madwifi.  

So I got the src rpm for Networkmanager and modified the current nm-wireless-driver-workarounds-rml.patch to have ndiswrapper set to apscan=1 instead of apscan=2.  Rebuilt Networkmanager and now I'm able to connect to both open and encrypted networks with ndiswrapper.

After additional testing with packages from Factory for rc3, I cannot connect to unencrypted APs if there is only one AP or several broadcasting the same id.  NM fails to get beyond stage 2.  The ratio of  connects to non connects is 1 to 50.  If there are numberous wireless broadcasts, AP and machines broadcasting (ad hoc) then creating a connection to an open AP is possable.  
When working with a single AP if I use wificonfig to do a scan while NM is stuck at 28% then the link will be created and an IP obtained.  Doing a Google search shows that others are still fighting this problem with other distributions.


Currently using ndiswrapper 1.15, the current NM and WPA from factory.