| 2008-06-07 00:32:52 |
Jérémy Subtil |
bug |
|
|
added bug |
| 2008-06-07 00:46:16 |
Jérémy Subtil |
description |
Binary package hint: wpasupplicant
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 (minor) 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? |
Binary package hint: wpasupplicant
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? |
|
| 2008-06-08 10:37:27 |
Jérémy Subtil |
marked as duplicate |
|
207446 |
|
| 2008-06-08 10:41:44 |
Jérémy Subtil |
description |
Binary package hint: wpasupplicant
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? |
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? |
|
| 2010-07-02 14:06:36 |
Jérémy Subtil |
removed subscriber Jérémy Subtil |
|
|
|
| 2013-09-07 20:47:29 |
penalvch |
removed duplicate marker |
207446 |
|
|
| 2013-09-07 20:49:40 |
penalvch |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2019-10-03 09:29:15 |
Po-Hsu Lin |
linux (Ubuntu): status |
Incomplete |
Won't Fix |
|
| 2019-10-03 09:29:17 |
Po-Hsu Lin |
wpasupplicant (Ubuntu): status |
New |
Won't Fix |
|
