Ubuntu
linux package

wpasupplicant associates only in precise conditions

Bug #238031 reported by Jérémy Subtil
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
wpasupplicant (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

This is a very weird bug. I'm using Ubuntu Hardy with a NETGEAR WG311v2 wifi card (Ndiswrapper driver). I try to connect to the AP through the command line because I wasn't able to make it work with network-manager, wicd or the GNOME network tool: connection was endless or timed-out.

With kernel 2.6.24-16, my wifi card only associates with the AP by the command line "sudo wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -d", but it doesn't with "sudo wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf" or "sudo wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -dd".

With kernel 2.6.24-18, it doesn't associates at all.

Thus, I'm suspecting wpasupplicant to connect to my AP too quickly (or slowly) when it fails, because association works only with a precise kernel version and a precise debugging level.

I'm using the same wpa_supplicant.conf template as provided in /usr/share/doc/wpasupplicant/examples/wpa-psk-tkip.conf.

Is this bug really related to wpasupplicant? Or is it ndiswrapper's kernel module? Is there a way to introduce a waiting time during the association process?

See original description
Jérémy Subtil (bigmadwolf)
description: updated
Revision history for this message
Reinhard Tartler (siretart) wrote :

this bug is likely to be a duplicate to bug #207446.

Since you indicate that your results depend on the exact kernel version, I'm reassigning this bug to the kernel.

Revision history for this message
Jérémy Subtil (bigmadwolf) wrote :

You're right, this is a duplicate of the mentioned bug, sorry for the noise. So what about reassigning bug #207446 to the kernel as well?

I tried to associate with the gutsy kernel as a workaround and now it works.

description: updated
Revision history for this message
penalvch (penalvch) wrote :

Jérémy Subtil, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
Changed in wpasupplicant (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.