damien.bergam...@free.fr schrieb:
| hi list,
| i have a problem with wpa2 and osx. i could connect to the ap
| if i force it to use wpa1 only. all other wpaprotos gives a :
| WPA2(PSK,unknown/TKIP,AES/TKIP)
| while scanning with airport and the association failed. the test
| cases and dmesg
On Fri, Feb 13, 2009 at 05:12:06PM +0100, Tim Saueressig, thepixelz.com wrote:
damien.bergam...@free.fr schrieb:
Because we are approaching release, I will probably stop
advertising PSK-SHA-256 by default for 4.5 (AFAIK, only OpenBSD
clients are currently capable of selecting this
Stefan Sperling schrieb:
On Fri, Feb 13, 2009 at 05:12:06PM +0100, Tim Saueressig, thepixelz.com wrote:
damien.bergam...@free.fr schrieb:
Because we are approaching release, I will probably stop
advertising PSK-SHA-256 by default for 4.5 (AFAIK, only OpenBSD
clients are currently
On Fri, Feb 13, 2009 at 05:39:24PM +0100, Tim Saueressig, thepixelz.com wrote:
Stefan Sperling schrieb:
The MacBook would always try to use WPA Enterprise no matter what.
There was no apparent way (at least in the GUI) to convince the
thing to just do WPA PSK instead.
ot: there is a way,
| hi list,
| i have a problem with wpa2 and osx. i could connect to the ap
| if i force it to use wpa1 only. all other wpaprotos gives a :
| WPA2(PSK,unknown/TKIP,AES/TKIP)
| while scanning with airport and the association failed. the test
| cases and dmesg could be found here:
| http
hi list,
i have a problem with wpa2 and osx. i could connect to the ap
if i force it to use wpa1 only. all other wpaprotos gives a :
WPA2(PSK,unknown/TKIP,AES/TKIP)
while scanning with airport and the association failed. the test cases
and dmesg
could be found here: http://sumi.thepixelz.com
6 matches
Mail list logo