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]
