ubuntu 8.10, network manager 0.7 failes to connect to wlan (ndiswrapper + wg311v2 + WPA)

[Roman Pach]

Binary package hint: network-manager

The network-manager can not connect to access point using WPA with ndiswrapper and wg311v2.

After the deinstallation of network-manager there is no problem
with connection when using /etc/network/interfaces and ifup.

package configuration:
  Ubuntu 8.10
  network-manager 0.7~~svn20081018t105859-0ubuntu1
  wpasupplicat 0.6.4.2
  ndiswrapper-common 1.52-1ubuntu1
  ndiswrapper-utils-1.9 1.52-1ubuntu1

[Alexander Sack (asac)]

please attach complete syslog after reproducing. also attach working /e/n/interfaces file as you said and tell me how long connecting takes with ifup manually.

[Roman Pach (romph)]

Hello,

I've measured the run time of ifup. Here is the result:

  root@linux5:/home/roman# time ifup wlan0
  ioctl[SIOCSIWPMKSA]: Invalid argument
  ioctl[SIOCSIWPMKSA]: Invalid argument

  real 0m0.901s
  user 0m0.168s
  sys 0m0.240s

There are some files attached.
These ones prefixed with ifup-* contain the information while activating
the WLAN with the static configuration from /etc/network/interfaces.

The rest with the prefix nm-* were created during the attempt of
network-manager to connect to the access point.

Please let me know, if you need more information.

[Alexander Sack (asac)]

would be more insteresting to see how long it takes until you can ping the outside world with ifup.

[Roman Pach (romph)]

I've tried it three times; with 8, 9 and 10 sec delay between ifup and
ping. The results are attached.

[Alexander Sack (asac)]

ok your timing looks quite ok.

Anyway, could you try the test packages from http://launchpad.net/~network-manager/+archive ? the give your card much more time to associate.

[Roman Pach (romph)]

I've installed the launchpad network-manager packages.
Unfortunately the network-manager still could not connect to wlan.
I attach the new syslog file.

There must be a reason why the ifup has no problems and network-manager
has. I'd rather suggest there are some issues with the communication
between the network manager and the wpa_supplicant.

I can see in the syslog the wpa_supplicant state machine could not setup
the communication with the access point. I think the software had enough
time to do it, so I can't believe we have timing problems.

[Alexander Sack (asac)]

most likely a driver bug not telling user space that association has happened.

Please test if running sudo dhclient wlan0 will give you an ip while NM is trying to connect. thanks.

[Roman Pach (romph)]

the results of 'dhclient wlan0' follow

root@linux5:/home/roman# dhclient wlan0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:0f:b5:07:5c:d5
Sending on LPF/wlan0/00:0f:b5:07:5c:d5
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
root@linux5:/home/roman# dhclient wlan0
There is already a pid file /var/run/dhclient.pid with pid 5591
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:0f:b5:07:5c:d5
Sending on LPF/wlan0/00:0f:b5:07:5c:d5
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[Roman Pach (romph)]

I've built in some debug messages in the src directory of
gnome-network-manager. The state machine wireless_get_icon() in the file
applet-device-wifi.c starts in state 'Attempting to join' and stays
there forever.

[Alexander Sack (asac)]

please check whether the NM packages in ~network-manager PPA help you (its 0.7 final) ... https://edge.launchpad.net/~network-manager/+archive

[Roman Pach (romph)]

I've updated the following packages from PPA:

network-manager Version: 0.7-0ubuntu1~nm1~intrepid1
libmbca0 Version: 0.0.3~bzr42-0ubuntu3~nm1
libnm-glib-dev Version: 0.7-0ubuntu1~nm1~intrepid1
libnm-glib0 Version: 0.7-0ubuntu1~nm1~intrepid1
libnm-util0 Version: 0.7~~svn20081018t105859-0ubuntu2~nm4
network-manager-gnome Version: 0.7-0ubuntu1~nm1~intrepid1

Then tested the network manager a few times. I could see the same issue,
no problems while connecting over ifup, and timeouts while trying it
with network manager.

Attached is the file syslog.

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem. Please reopen it if you encounter that this issue is still occurring in latest Ubuntu Karmic version. To reopen the bug report you can click under the Status column, and change the Status back to "New". Thanks again!