Bug#428785: [pkg-wpa-devel] Bug#428785: wpasupplicant: losing WiFi connectivity Connection to wpa_supplicant lost - trying to reconnect
Reinhard Tartler [EMAIL PROTECTED] writes: Sebastian Niehaus [EMAIL PROTECTED] writes: For some reason, wpa_supplicant sometimes loses the connection to wpa_cli and wpa_supplicant seems to crash. It's rather the other way round: wpa_supplicant seems to crash for you, and wpa_cli looses therefore the connection. Please try to find out why it crashes for you. Please try to retrieve a coredump and backtrace. Tried to get e backtrace after recompile but I did not succeed, whatever I tried. Then I hypothesized wpa_supplicant could be stopped by some different process. I started fiddeling with whereami and ifplugd. Deinstalling whereami did not solve my problem so I modified the configuration of ifplugd which was ,[ /etc/default/ifplugd ]-- | INTERFACES=all | HOTPLUG_INTERFACES=all | | ARGS=-q -f -u0 -d10 -w -I | SUSPEND_ACTION=stop ` Now it is ,[ /etc/default/ifplugd ]-- | INTERFACES=eth0 eth1 | HOTPLUG_INTERFACES=eth0 | | ARGS=-q -f -u0 -d10 -w -I | SUSPEND_ACTION=stop ` where eth0 is my (wired) ethernet and eth1 the Intel Wireless LAN Adapter. I did not test the ethernet but WLAN runs fine for nearly 24 hours without wpa_supplicant disappearing somehow. I will test this setting longer ... Actually, I believe, the problem I reported is not a bug of wpa_supplicant, but a bad interaction of wpa_supplicant and ifplugd causing wpa_supplicant to be killed during bad WLAN connecticity. If others can reproduce this behaviour it may be useful to add this to the package's documentation. So long thanks a *lot* Sebastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428785: [pkg-wpa-devel] Bug#428785: wpasupplicant: losing WiFi connectivity Connection to wpa_supplicant lost - trying to reconnect
Reinhard Tartler [EMAIL PROTECTED] writes: Sebastian Niehaus [EMAIL PROTECTED] writes: Reinhard Tartler [EMAIL PROTECTED] writes: [...] Then I hypothesized wpa_supplicant could be stopped by some different process. I started fiddeling with whereami and ifplugd. Err, you didn't say before that you are using ifplugd and whereami at all. Sorry, my fault. This means that you don't use the ifupdown.sh integration we ship in the wpasupplicant package at all? Not sure, what started wpa_supplicant. Probably, it was ifup. On Sarge I used the init-script to start wpa_supplicant. This has disappeared on Sarge. After reading ,[ /usr/share/doc/wpasupplicant/README.Debian ] | | wpasupplicant is now integrated into ifupdown. You can configure it in | /etc/network/interfaces, in a similar method to configuring WEP keys[1]. | After that, wpa_supplicant will be controlled by ifupdown without further | user intervention. | ` i just left anything alone and most of the stuff seemed to work. Not very stable ... If you do, I think that would be the problem. I don't think that ifplugd can be used reasonably with our /e/n/i integration. It was designed to replace the ifplugd functionality, so there is no real point in it. Okay. It seems it works now for me with ifplugd running at the config I posted earlier. If there are further problems, I will remember your words to track down the issue. Perhaps we can make this point in the documentation more clear... Maybe. After reading the docs I was not very sure how to integrate wpa_supplicant at all. Anyways, I consider this bug to be solved. Thank you /very/ /much/ for your support, Sebastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428785: [pkg-wpa-devel] Bug#428785: wpasupplicant: losing WiFi connectivity Connection to wpa_supplicant lost - trying to reconnect
Sebastian Niehaus [EMAIL PROTECTED] writes: Reinhard Tartler [EMAIL PROTECTED] writes: Sebastian Niehaus [EMAIL PROTECTED] writes: For some reason, wpa_supplicant sometimes loses the connection to wpa_cli and wpa_supplicant seems to crash. It's rather the other way round: wpa_supplicant seems to crash for you, and wpa_cli looses therefore the connection. Please try to find out why it crashes for you. Please try to retrieve a coredump and backtrace. Tried to get e backtrace after recompile but I did not succeed, whatever I tried. Then I hypothesized wpa_supplicant could be stopped by some different process. I started fiddeling with whereami and ifplugd. Err, you didn't say before that you are using ifplugd and whereami at all. This means that you don't use the ifupdown.sh integration we ship in the wpasupplicant package at all? If you do, I think that would be the problem. I don't think that ifplugd can be used reasonably with our /e/n/i integration. It was designed to replace the ifplugd functionality, so there is no real point in it. Perhaps we can make this point in the documentation more clear... -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428785: [pkg-wpa-devel] Bug#428785: wpasupplicant: losing WiFi connectivity Connection to wpa_supplicant lost - trying to reconnect
Reinhard Tartler [EMAIL PROTECTED] writes: Sebastian Niehaus [EMAIL PROTECTED] writes: For some reason, wpa_supplicant sometimes loses the connection to wpa_cli and wpa_supplicant seems to crash. [...] Please try to find out why it crashes for you. Please try to retrieve a coredump and backtrace. Please don't kill me for stupid question: how do generate a coredump and a backtrace? Sincerely, Sebastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428785: [pkg-wpa-devel] Bug#428785: wpasupplicant: losing WiFi connectivity Connection to wpa_supplicant lost - trying to reconnect
Sebastian Niehaus [EMAIL PROTECTED] writes: Please don't kill me for stupid question: how do generate a coredump and a backtrace? * recompile the wpasupplicant package with the environment DEB_BUILD_OPTIONS=nostrip * Start a shell and issue 'ulimit -c unlimited'. * Run wpasupplicant from hand in the same shell with correct parameters. * If the problem reappears, send it a abort signal like this: 'kill -6 `pidof wpa_supplicant`' * a file 'core' should be created in the current directory * run gdb: 'gdb /sbin/wpa_supplicant core' * create a backtrace: 'bt' Attach that output. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428785: [pkg-wpa-devel] Bug#428785: wpasupplicant: losing WiFi connectivity Connection to wpa_supplicant lost - trying to reconnect
Sebastian Niehaus [EMAIL PROTECTED] writes: For some reason, wpa_supplicant sometimes loses the connection to wpa_cli and wpa_supplicant seems to crash. It's rather the other way round: wpa_supplicant seems to crash for you, and wpa_cli looses therefore the connection. Please try to find out why it crashes for you. Please try to retrieve a coredump and backtrace. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
