You are not logged in.
Hi,
Since kernel 2.6.27 ath9k was deemed stable enough to be included in the kernel. So I've tried to use it with every new kernel-release and still I get the same problems: connection time outs, packet loss once connected, slow speeds etc.
Connecting with ndiswrapper is a breeze, even with wpa_supplicant. Speeds are good.
Am I the only one here? Is this Arch-specific or kernel-related?
THX!
Zl.
PS I have ruled out several other factors: netcfg doesn't influence the situation, nor usage of wpa_supplicant-beta, nor dhcpcd vs dhclient.
Last edited by zenlord (2009-01-28 10:56:04)
Offline
problems here too....
One network I use frequently uses wpa2 with a certificate. In All but two buildings I have no problems connecting and authenticating. In the two buildings in which I have trouble wpa_supplicant appears to authenticate properly except for the following
OpenSSL: tls_connection_handshake - Failed to read possible Application Data error:00000000:lib(0):func(0):reason(0)I can acquire and ip but ping'ing a www times out.
wpa_supplicant stuff
wpa_supplicant -Dwext -iwlan0 -cwpa_supplicant.conf
<config>
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network{
ssid="****"
key_mgmt=WPA-EAP
pairwise= CCMP TKIP
group= CCMP TKIP
eap=PEAP
identity="***"
password="***"
ca_cert="***.pem"
phase1="peaplable=0"
phase2="auth=MSCHAPV2"
}I've googled this to death over the past 5 months with no luck.
thanks for any help
Offline
Hello folks.
I too have a question concerning wpa_supplicant and ath9k. I have an atheros ar928x adapter and I would like to know which driver I should hand over as an argument for wpa_supplicant? Madwifi? Wext? Or ath9k? But ath9k is not listed as a possible argument for wpa_supplicant.
Thanx for any suggestion.
Last edited by hauntergeist (2009-07-04 22:06:29)
Offline
Wext works for me. There may be some compatability with madwifi, but I've never heard anything about it
Offline
I thought wpa_supplicant should always be used with wext. Works for me.
Offline