On Tue, Jul 19, 2011 at 03:24:29PM +0200, Stefan Assmann wrote:
> On 18.07.2011 17:44, Larry Finger wrote:
> > On 07/18/2011 10:01 AM, Stefan Assmann wrote:
> >> On 18.07.2011 16:53, Larry Finger wrote:
> >>> On 07/18/2011 03:46 AM, Stefan Assmann wrote:
> >>> Please post your wpa_supplicant.conf. In particular, what is the value for
> >>> scan_ssid?
> >>
> >> ctrl_interface=/var/run/wpa_supplicant
> >> eapol_version=1
> >> ap_scan=2
> >>
> >> network={
> >> ssid="<ssid>"
> >> id_str="<ssid>"
> >> priority=5
> >> proto=RSN
> >> key_mgmt=WPA-PSK
> >> psk=<psk>
> >> }
> >>
> >> Should I try again with scan_ssid=1 ? From reading the man page this
> >> makes a difference if the ssid is hidden, which is not the case.
> >
> > Yes. It also changes the scan behavior.
>
> So far I can say that with scan_ssid=1 after rebooting the AP the
> connection is properly re-established. Looks promising.
I have not yet managed to reproduce your problem, unfortunately. I
will watch for it, though.
regards,
ali
> Stefan
>
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
