[ndiswrapper] network manager in roaming mode fails to connect to wpa network using ndiswrapper

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the /var/log/syslog to your bug report as an attachment? Also you can submit more information for it by looking to https://wiki.ubuntu.com/DebuggingNetworkManager , Thanks in advance.

Pedro Villavicencio wrote:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. Could you please add the /var/log/syslog to your bug report as
> an attachment? Also you can submit more information for it by looking to
> https://wiki.ubuntu.com/DebuggingNetworkManager , Thanks in advance.

It may be a month or so before I can get the information. I had to
reinstall Gutsy to get a working system. I'm also going to repartition
the system so that I can get Hardy on another partition to do testing.

Please don't remove this bug.

having similar problem, here's my syslog

I had to reinstall Gutsy to do work on the system, then after several failed install attempts (due to issues not related to Ubuntu), I finally got Hardy installed on a partition for testing and to fill out more information in the bug report here, and it started working again.

I have no idea why it started working again the only difference was I marked the system to not install backport or postponed updates.

Just today the same issue started happening again... This is what I found over and over again on every single connection attempt:

May 12 19:34:20 althor kernel: [ 445.912997] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May 12 19:34:28 althor dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.host_name
May 12 19:34:28 althor dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_domain
May 12 19:34:28 althor dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_servers
May 12 19:34:28 althor dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.interface_mtu

I don't know if this has anything to do with things or not.

same to me!

Hardy 8.04 updated
Ndiswrapper 1.52
driver bcmwl5
03:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)

messages log:

May 27 09:19:13 HHFT kernel: [ 9038.666221] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 27 09:19:19 HHFT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
May 27 09:19:19 HHFT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
May 27 09:19:19 HHFT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
May 27 09:19:19 HHFT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.interface_mtu

More complete log:

May 27 09:11:13 HHFT kernel: [ 8488.312493] ndiswrapper version 1.52 loaded (smp=yes, preempt=no)
May 27 09:11:13 HHFT kernel: [ 8488.350721] ndiswrapper: driver bcmwl5 (Broadcom,07/11/2007, 4.150.29.0) loaded
May 27 09:11:13 HHFT kernel: [ 8488.353231] ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LK4E] -> GSI 19 (level, high) -> IRQ 16
May 27 09:11:13 HHFT kernel: [ 8488.359478] ndiswrapper: using IRQ 16
May 27 09:11:13 HHFT kernel: [ 3771.393712] wlan0: ethernet device 00:1a:73:46:4a:bb using NDIS driver: bcmwl5, version: 0x4961d00, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4311.5.conf
May 27 09:11:13 HHFT kernel: [ 3771.394613] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
May 27 09:11:13 HHFT kernel: [ 3771.395593] usbcore: registered new interface driver ndiswrapper
May 27 09:11:13 HHFT kernel: [ 3771.413048] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 27 09:11:14 HHFT kernel: [ 8490.458264] eth0: link down.
May 27 09:11:51 HHFT kernel: [ 8528.667538] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May 27 09:14:19 HHFT kernel: [ 8692.473630] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May 27 09:16:33 HHFT kernel: [ 8847.662971] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May 27 09:17:48 HHFT kernel: [ 8939.652712] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May 27 09:19:13 HHFT kernel: [ 9038.664053] eth0: link up.
May 27 09:19:13 HHFT kernel: [ 9038.666221] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 27 09:19:19 HHFT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
May 27 09:19:19 HHFT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
May 27 09:19:19 HHFT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
May 27 09:19:19 HHFT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.interface_mtu

Got the same problem with Intel Pro BG9435 wireless card. Once I reset the AP , it connects but next restart it keeps throwing the message below in /var/log/messages.

May 28 23:30:04 sparta dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
May 28 23:30:56 sparta dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
May 28 23:31:43 sparta dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name
May 28 23:31:43 sparta dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
May 28 23:31:43 sparta dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
May 28 23:31:43 sparta dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.interface_mtu
May 28 23:31:44 sparta dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
May 28 23:32:25 sparta dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason

network manager has a high bar for drivers, which ndiswrapper appears to not provide yet.

My system, which worked fine since the Hardy release, now has the same symptoms. I can only think an update in the last three days borked ndiswrapper/wpa_supplicant. From /var/log/messages:

Jul 3 16:59:16 goinmobile kernel: [ 246.613083] usbcore: registered new interface driver ndiswrapper
Jul 3 17:00:00 goinmobile dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
Jul 3 17:00:44 goinmobile dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 3 17:00:44 goinmobile dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 3 17:00:44 goinmobile dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.interface_mtu

My wireless chipset is a Broadcom Airport One, BCM4318, Rev. 2.

Ubuntu 8.04 in a notebook Amazon PC.
I have de same problem, even i put the wired network (eth0) on fixed ip or in DHCP.

My solution was put the wired network (eth0) in roaming mode, then my internet work's fine with the wlan0.

I have a similar problem, unencrypted and WEP work fine but WPA won't conect. If you need any information from me just ask for it, i have subscribed to this bug.

I have the same problem with a Texas Instruments ACX 111 wireless chipset. Without WPA I can't use my wireless network, I'd really like to see this bug fixed some time soon...

Just uninstalled apt's ndiswrapper, installed latest ndiswrapper from svn and Wicd, and WPA started working. Maybe you should try that?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I have tried that, no go on my end. I had to use the Atheros drivers
for my card, which while work with well designed and implemented Atheros
chipsets, my card is slightly... Less... Than well designed, I'm
getting frustrated enough to do some of my high speed network tasks
in... (almost vomits) Windows or on my wife's mac.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIhTCl3fPbFEOFPCwRCIxxAJ0XJoz2uu3nh35iT1/1FMEXR9F3FQCfTk1g
gEompTLthr5LjL+1P3bwseo=
=3n8J
-----END PGP SIGNATURE-----

Hi,

Same symptoms here with Gutsy / 2.6.24.3 / AR5006EG / ndiswrapper 1.53./ XP driver

It sometimes cannot connect at boot. It seems that after a while (10mn), the link becomes ready. Sometimes, I try to connect with Wifi-radar during this time. I am not sure this helps. I think that there is a timeout somewhere in the process and after, the links becomes ready.

No hard freeze / just lost of time waiting for wifi waking-up.

/var/log/message
=========
Aug 6 09:41:18 IT kernel: [ 602.107150] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Aug 6 09:42:43 IT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
Aug 6 09:42:47 IT kernel: [ 649.233207] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Aug 6 09:42:50 IT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.host_name
Aug 6 09:42:50 IT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.domain_name
Aug 6 09:42:50 IT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_domain
Aug 6 09:42:50 IT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_servers
=========

My card : Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)

I did not try in Hardy by the way.

Philippe

Let me add my troubles to this, but IM not experienced in any way with ubuntu...
Wireless worked fine last night, then i restarted and all the suddon it's not working...

Log message [probably more then one message] =
Aug 30 23:41:15 ty-laptop kernel: [ 120.067771] NET: Registered protocol family 17
Aug 30 23:45:22 ty-laptop kernel: [ 292.073948] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Aug 30 23:45:22 ty-laptop kernel: [ 292.084155] eth0: link down
Aug 30 23:45:22 ty-laptop kernel: [ 292.085812] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 30 23:46:05 ty-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.reason
Aug 30 23:46:07 ty-laptop kernel: [ 326.615528] ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
Aug 30 23:50:28 ty-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.reason
Aug 30 23:59:58 ty-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.reason

it works flawlessly with wired, even tried connecting to a different wireless network, the network i was connecting to was UNSECURE.

I have a similar sounding problem with BCM4306 rev 2 hardware on a WPA AP.
It never connects, just keeps asking for password.
I have documented this with re-createable steps in a completely Live-CD environment.
It works in Gutsy, but is broken in Hardy and Intrepid (I have tested Intrepid Alpha 5 and 6).
I have submitted bug #276980 against my hardware and with steps to re-create on Live-CD.
https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/276980

I have similar problem with atheros AR5212 in Interpid. It worked in Hardy.
It doesnt connect to a WPA network. Just asks for the password all the time. Logs say "authorisation timeout", but it doesnt even wait so long.

I forgot to mention, its with kernel drivers, not ndiswrapper.

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release (10.04 or 10.10)? Thanks in advance.

[Expired for ndiswrapper (Ubuntu) because there has been no activity for 60 days.]