Re: [ath9k-devel] [OpenWrt-Devel] ath9k (ad-hoc?) problems in compat-wireless trunk as of sept 6/2

2013-09-15 Thread Felix Fietkau
On 2013-09-09 1:29 PM, Nicolás Echániz wrote:
 I have kept testing this and was able to reproduce the same problem
 every time.
 The performance perception when the network is at rush hour is very
 unstable so I tried to reproduce traffic conditions during late night.
 I sent multiple netperfs through different routes and while the netperfs
 were running turned of one node. Latency climbed to the thousands and it
 took a while for it to stabilize again.
 
 Then I turned off another node, latency went sky high again for some
 seconds until I lost conectivity and could monitor no more.
 
 I waited more than 15 minutes for the net to be reachable again from my
 local node. (Nodes are automatically reset when they cannot reach the
 network gateway for more than 15 minutes)
 
 All ping tests are done on fe80 local IPv6 addresses so no routing
 protocol is involved in case someone's wondering. Also, from what I see
 (iw station dump), routers are associated but can send no data.
I've committed some fixes that might be related to this issue. Please
test current OpenWrt trunk.

Thanks,

- Felix

___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel


Re: [ath9k-devel] ath9k WPA2-PEAP MSCHAPV2 Connectivity issue

2013-09-15 Thread Holger Schurig
 Please use -Dnl80211 with wpa_supplicant. WEXT has been deprecated for
 a number of years.

Probably wpa_supplicant should, in it's devel branch, make this to be
-Ddeprecated_wext. That way Linux distributions that blindly
recompile things and don't think are forced to do something :-)  Or
scrap the WEXT support in the devel-branch totally ...
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel