Hi Bernhard,
On Saturday 17 March 2007 16:47, Bernhard wrote:
> Hello,
>
> This bugreport stays at "more information needed".
> Which additional information is needed?
>
> Please let me know.
This bug report caught me by surprise, it seems that is was transferred over
here from another package.
I have read the bug history, but have found no really substantial information
about the claim that "wireless_essid FOO" (using wireless-tools) is required
for operation of wpa_supplicant. However, I suspect that the massive revamp
of the wpasupplicant package that happened before etch is what is confusing
matters here.
Please first start by looking at:
/usr/share/doc/wpasupplicant/NEWS.Debian.gz
Starting from version 0.4.8, a system wide, individual wpa_supplicant process
is no longer available. Rather, settings for WPA are done (similarly to
wireless-tools) via wpa-ssid SSID, wpa-psk PSK, wpa-* BAR etc. lines
in /etc/network/interfaces.
Take a look at the following for a description of how this new schema works:
/usr/share/doc/wpasupplicant/README.modes.gz
For example, my desktop machine has something similar to:
auto eth1
iface eth1 inet dhcp
wpa-ssid MyNet
wpa-psk secretpasswordformynet
in /etc/network/interfaces, and when ifupdown starts at boot time
wpa_supplicant is started with the above configuration and my connection is
negotiated.
If neither of the mentioned documents sheds any more light on your problem,
please describe your WPA setup a bit more:
How is wpa_supplicant started?
What is the content of your wpa_supplicant configuration, and where is it
located?
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
