Re: wpa_supplicant and ssid
On Monday, October 18, 2010 18:55:34 you wrote: It seems that wpa_supplicant iterate through all scanned ssids and try to associate with each, and that cause two problem for me. 1) in my school, there are many AP, and connection is not stable, when disconnect, it take many time to try and fail to associate with those ssids until the one I want. You can add a 'priority' statement to each network block in wpa_supplicant.conf. 2) i can't associate with a non-discoverable ssid but probably it is my wireless driver's problem, i'm using bwn0 and currently I need to force it to use mode 11b or it is unusable. Tried different options for the scan_ssid parameter? or should I complain to upstream ? Before doing so, can you capture the output of 'wlandebug 0x' while trying to get a connection? -- Bernhard ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wpa_supplicant and ssid
On Tue, 2010-10-19 at 00:55 +0800, Buganini wrote: It seems that wpa_supplicant iterate through all scanned ssids and try to associate with each, and that cause two problem for me. 1) in my school, there are many AP, and connection is not stable, when disconnect, it take many time to try and fail to associate with those ssids until the one I want. This appears to be the same as the bug reported in PR bin/98220. wpa_supplicant is contributed code, so I think the correct answer is to report this upstream. As far as I could tell when I last checked, this hasn't yet been fixed upstream. Gavin -- Gavin Atkinson FreeBSD committer and bugmeister GPG: A093262B (313A A79F 697D 3A5C 216A EDF5 935D EF44 A093 262B) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
wpa_supplicant and ssid
It seems that wpa_supplicant iterate through all scanned ssids and try to associate with each, and that cause two problem for me. 1) in my school, there are many AP, and connection is not stable, when disconnect, it take many time to try and fail to associate with those ssids until the one I want. 2) i can't associate with a non-discoverable ssid but probably it is my wireless driver's problem, i'm using bwn0 and currently I need to force it to use mode 11b or it is unusable. or should I complain to upstream ? -- Buganini ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
