Your message dated Sun, 1 Jul 2012 16:48:26 +0200 with message-id <[email protected]> and subject line Re: wpasupplicant: Wpasupplicant works only good if I start it with low Priority has caused the Debian Bug report #471905, regarding wpasupplicant: Wpasupplicant works only good if I start it with low Priority to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 471905: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471905 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: wpasupplicant Version: 0.6.3-1 Severity: important Hi, if I start or configure wpasupplicant with normal priority, it is not possible to establish the WPA2 or WPA connection. But a simple nice -10 in pre-up solve the problem completely. The problem exists only in the daemon mode. In debug mode I didn't have any problems. Here is my temporary solve (work perfekt): /etc/network/interfaces allow-hotplug wlan0 iface wlan0 inet dhcp pre-up nice -19 wpa_supplicant -B -i wlan0 -c "/etc/wpa_supplicant/wpa_supplicant.conf" -D wext; sleep 10; post-down killall -q dhclient wpa_supplicant; I worked at thy moment with ndiswrapper and the wext driver. I test it on three different systems with stable, testing and unstable version of wpasupplicant. Two slow systems haves the problem. (ndiswrapper WG111v3) One new system with kernel rtl8187 driver works fine without any hotfixes. Here is the udev rule from the worked system without any hotfixes: # USB device 0bda:8187 (rtl8187) SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:15:af:04:ac:37", ATTR{type}=="1", NAME="wlan0" For this both systems i need the "nice" low priority. # USB device 0846:4260 (ndiswrapper) SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1b:2f:d2:94:e8", ATTR{type}=="1", NAME="wlan0" # USB device 0846:4260 (ndiswrapper) SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1b:2f:d2:94:f1", ATTR{type}=="1", NAME="wlan0" -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (700, 'testing'), (40, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages wpasupplicant depends on: ii adduser 3.106 add and remove users and groups ii libc6 2.7-6 GNU C Library: Shared libraries ii libdbus-1-3 1.1.2-1 simple interprocess messaging syst ii libpcsclite1 1.4.99-2 Middleware to access a smart card ii libreadline5 5.2-3 GNU readline and history libraries ii libssl0.9.8 0.9.8g-4 SSL shared libraries ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip wpasupplicant recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message ---reassign 471905 ndiswrapper thanks Hi On Wednesday 23 May 2012, Stefan Lippers-Hollmann wrote: > On Wednesday 23 May 2012, Gregor Adamczyk wrote: > > Hi, if I start or configure wpasupplicant with normal priority, it is not > > possible to establish > > the WPA2 or WPA connection. > > > > But a simple nice -10 in pre-up solve the problem completely. > > > > The problem exists only in the daemon mode. > > > > In debug mode I didn't have any problems. > > > > Here is my temporary solve (work perfekt): > > > > /etc/network/interfaces > > > > allow-hotplug wlan0 > > iface wlan0 inet dhcp > > pre-up nice -19 wpa_supplicant -B -i wlan0 -c > > "/etc/wpa_supplicant/wpa_supplicant.conf" -D wext; > > sleep 10; > > post-down killall -q dhclient wpa_supplicant; > > > > I worked at thy moment with ndiswrapper and the wext driver. > […] > > Is this still a problem for you? > > Looking through the bugreport and the involved source, I strongly > suggest that this is a ndiswrapper problem, rather than a bug in > wpasupplicant (the kernel module really needs to accept commands in > order), but before reassigning, I'd like to reconfirm that this is > still open. No response within the last >month, reassigning and closing. Regards Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
