Bug#409076: New WPA configuration

2007-04-05 Thread Bernhard
Hello, Kel

I have tested it with my Notebook again.

My new configuration of the network interface is shown in the following
lines:
   iface eth2 inet dhcp
   wpa-ssid mynetworkessid
   wpa-psk mysecretpassword
   wireless-essid mynetworkessid

With the configuration above, a connection to my access point is
established.
Without the wireless-essid, no connection to the access point is
established.

I see, that the severity of this bug report stays at "Normal".
Because this is not a really issue, you can set this bug report to
"Minor" or "Wishlist item".

Questions from my side with this kind of configuration:
Is the content of /etc/wpa_supplicant/wpa_supplicant.conf ignored?
Which driver is used as default, if the parameter wpa-driver is not set?

If you need more information, let me know.
Thank you for the support.

Regards
Bernhard



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#409076: [pkg-wpa-devel] Bug#409076: New WPA configuration

2007-04-07 Thread Kel Modderman
Hi Bernhard,

On Friday 06 April 2007 04:39, Bernhard wrote:
> Hello, Kel
>
> I have tested it with my Notebook again.
>
> My new configuration of the network interface is shown in the following
> lines:
>iface eth2 inet dhcp
>wpa-ssid mynetworkessid
>wpa-psk mysecretpassword
>wireless-essid mynetworkessid
>
> With the configuration above, a connection to my access point is
> established.
> Without the wireless-essid, no connection to the access point is
> established.

That implies that wpa_supplicant somehow is not able to associate with the 
access point in question by itself, which is strange.

>
> I see, that the severity of this bug report stays at "Normal".
> Because this is not a really issue, you can set this bug report to
> "Minor" or "Wishlist item".

I think the current severity is ok. It could be that you have found a severe 
problem that stops wpa_supplicant from operating properly with your hardware, 
or it could be a simple mis-configuration.

>
> Questions from my side with this kind of configuration:
> Is the content of /etc/wpa_supplicant/wpa_supplicant.conf ignored?

Yes. As described in /usr/share/doc/wpasupplicant/README.modes.gz section "How 
It Works".

> Which driver is used as default, if the parameter wpa-driver is not set?

wext, as per section "1. Specifying the wpa_supplicant driver backend" 
of /usr/share/doc/wpasupplicant/README.modes.gz.

>
> If you need more information, let me know.
> Thank you for the support.

I think what needs to happen is manual debugging of wpa_supplicant. You may 
start the supplicant by hand with your old config file 
(/etc/wpa_supplicant/wpa_supplicant.conf) with '-ddd' as an option, like:

wpa_supplicant -Dwext -ieth2 -c/etc/wpa_supplicant/wpa_supplicant.conf -ddd

Capture the debug output and paste it into a text file. This assumes that the 
daemon has not already been started by another method, so ifdown the 
interface, make sure no wpa_supplicant processes are running before trying to 
debug.

Please also disclose the contents of /etc/wpa_supplicant/wpa_supplicant.conf 
and describe what hardware is used at client and access point side, what 
level of encryption is employed etc etc.

Thanks, Kel.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]