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]
