Re: [ath5k-devel] ath5k 10db less than madwifi driver :-(
Hello First of all I changed today the WLM54AGP23 card to CM9 and same result. I tried also WLM200NX and with this card nor clients in 2.4GHz nor in 5GHz connects but this test was only rudimentary... Will have to see again in labor ... BUT CM9 and WLM54AGP23 has the same issue so it's definitvly a driver or hostapd problem ... On 11/15/2013 08:21 PM, Nick Kossifidis wrote: 2013/11/15 Beat Meier mbe...@swiss-wireless.com.ar: Hello again Have done a lot of tests and there is no chance. WLM54AGP23 in the 2.4GHz band does not work right... What I see is that if hostapd using ath5k and WLM54AGP23 clients with madwifi and WLM54AGP23 will not connect in outdoor environment I have enabled debugfs but don't see anything. How can you see if a cliente tries to connect? At the end I will put the output of kernel.log Using any mode of any (disable/high/low) does not change anything. Not for the only connected client signal nor will connect any other client. In the labor I have no problems apart from lower signal put outdoor it does not work... My clients signal on the outdoor have the following signals on madwifi... X: -80 # this is the only which connects to ath5k driver too Y: -76 Z: -68 Nor Y nor Z connect to ath5k driver (y,z use madwifi) Try running hostapd in foreground with verbose debugging on, this sounds more like a hostapd bug than a driver bug, also the signal i think is not relevant here, maybe X is the first that tries to connect or something. Try to debug this further please, if you have only Y or only Z do they connect ? I have other client which will connect which don't have madwifi... I need to install a system with ath5k instetad of madwifi as client and see ... I don't think this is a hostapd problem because i have no associacion in debug level of driver or am I wrong that I must see the driver first befor hostapd? I have the messages moving STA XX to state Y and the only one is the connected one... I thought ath5k drive will put this because I enabled debuging of driver but must have a closer look... Other strange behaviout is that I cannot enable ath5k debugging in debugfs... I have to instert the parameter loading the module i.e. cd /sys/kernel/debug/ieee80211/phy0/ath5k echo 0x debug does not work.. debug is still on 0 BTW: I'm using kernel-3.8.13 More strange the tests below... I really don't know were to go... Any help with this cards??? Here my output tests of the labor ### CM9 Tetst Channel 1 on master (CM9/19dbm): madwifi -34 with wlanconfig on sta (CM9/19dbm): ath5k -30 with wlanconfig # set txpower betwenn 15-19db same signal on master What do you mean ath5k with wlanconfig ? wlanconfig is a madwifi related tool, to play with ath5k you should use iw. Sorry... Cut paste error from old tests.. of course iw... on master (CM9/19dbm): madwifi -29 with wlanconfig on sta (CM9/19dbm): madwifi -32 with wlanconfig # set txpower to 19 on master (CM9/19dbm): ath5k -31 with wlanconfig on sta (CM9/19dbm): madwifi -36 with wlanconfig # set txpower to 19 echo sens-high ani on master not anymore connection possible from client with madwifi not even after setting ani-on and restart interface!! on master (CM9/19dbm): ath5k -39 / 3.9Mbps on sta (CM9/19dbm): ath5k -33 / 3.1Mbps Without trafic signal on client drops to -77!! Setting all 4 ani states on master and restart interface does not change signal nor on client nor on master The same on client (while on master ani off) I noticed that in all your tests above the signal strength is too much. If a signal is too strong (-40 and above, depends on the card) it may result distortion on the receive path and result lower throughput. Signal strength is measured at the entry of the phy chain, before any processing is being done, you can have great signal but no traffic at all -e.g. because your intermediate frequency is jammed or gets a lot of noise-. Also giving a high tx power might also result distortion on the tx path. To make sure that's not the case please make sure you have a tx power around 15db to begin with and that the signal strength on your receiver is -60 to -77 and retest. I had never problems in the past nor with madwifi nor with ubuiquity... I do tests with signal o -15 in the labor no problem with madwifi ... Will do test as you noted nevertheless!! WLM54AGP23 ** Channel 1-6 does not work with ath5k ping time about 700-3000ms trafic about 100kbps I have changed both cards the new one the same effect so no card is defect!!! On outdor this channel works... More than strange to me!!! Maybe because the signal strength is too much indoors (see above) ;-) Channel 7-11 works on master (WLM54AGP23/23dbm): ath5k -36 / 3.9Mbps on sta (WLM54AGP23/23dbm): ath5k -26 with trafic goese to -32 / 3.1Mbps scanning shows ap with signal of -29 without trafic signal
Re: [ath5k-devel] ath5k 10db less than madwifi driver :-(
Yes transmit power is not an issue. I will to tests with CM9 again and post the infos. Beat On 10/30/2013 07:08 PM, Nick Kossifidis wrote: On 10/30/2013 06:54 PM, Beat Meier wrote: Hello I have a lot of wireless repeaters which uses madwifi. Because of several problem like not anymore supported and other problems like no xmit buf I need to upgrade to mac80211 with ath5k. What I notice is that in the b band the ath5k driver has about 10dbm less than madwifi driver and a band too. It's not the noise it have really 10db difference. Nobody having this problem with long distance links? This is with Compex cards, CM9 ... Because of this I have bad througput (signal of -80) instead of -70 with madwifi and good througput. Any ideas what could be wrong and how to debug the issue??? Greetings ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel Are you sure you are allowed to transmit at that power level ? ath5k/mac80211 use crda and the wireless regulatory db to determine the maximum allowed transmission power. Start by verifying the allowed power limits by the driver (you should see a list on dmesg or with iw) and then if it's not related we can see if it's a driver bug. From my tests CM9s work fine with ath5k. ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
Re: [ath5k-devel] ath5k 10db less than madwifi driver :-(
Denis What version of madwifi are you using? Do you don't have problems with discrad, no xmit buf? This is one of my biggest problem today to stay with madifi :-( Greetings Beat On 10/30/2013 04:04 PM, Denis Periša wrote: I also see power issue.. or HAVE seen.. I've switched back to madwifi ... it's superior. bw40 mode is also something I cannot get by. I was very disappointed with ath5k I must admit. On Wed, Oct 30, 2013 at 7:54 PM, Beat Meier mbe...@swiss-wireless.com.ar mailto:mbe...@swiss-wireless.com.ar wrote: Hello I have a lot of wireless repeaters which uses madwifi. Because of several problem like not anymore supported and other problems like no xmit buf I need to upgrade to mac80211 with ath5k. What I notice is that in the b band the ath5k driver has about 10dbm less than madwifi driver and a band too. It's not the noise it have really 10db difference. Nobody having this problem with long distance links? This is with Compex cards, CM9 ... Because of this I have bad througput (signal of -80) instead of -70 with madwifi and good througput. Any ideas what could be wrong and how to debug the issue??? Greetings ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org mailto:ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
[ath5k-devel] ath5k 10db less than madwifi driver :-(
Hello I have a lot of wireless repeaters which uses madwifi. Because of several problem like not anymore supported and other problems like no xmit buf I need to upgrade to mac80211 with ath5k. What I notice is that in the b band the ath5k driver has about 10dbm less than madwifi driver and a band too. It's not the noise it have really 10db difference. Nobody having this problem with long distance links? This is with Compex cards, CM9 ... Because of this I have bad througput (signal of -80) instead of -70 with madwifi and good througput. Any ideas what could be wrong and how to debug the issue??? Greetings ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
[ath5k-devel] Clients won't connect. Debug output. How to go on? Any help?
Hello I try to debug ath5k because most clients will not connect. The only client which connects is 00:27:22:92:d2:50, which has also debug entries. Debug was created with modprobe ath5k debug=0x and removed beacons common messages Ani is enabled. Same result with ani disabled... So my questions. If a clients has not so much signal does they appear in the debug log of ath5k or on which layer is this? I thought ath5k is the first layer of wireless connection point from a client, I'm I wrong or is there other debug level? BTW: I'm using ath5k of kernel 3.8.13. How can I try new versions of ath5k with this kernel? I see wireless-compat, wireless-testing.git, wireless-next-2.6.gi, wireless-2.6.git but I have no idea were to go :-( Should I open a ticket for my problem? Any help? BTW: Is there no way to enable debuging ath5k in the debugfs? I tried echo 0x /sys/kernel/debug/ieee80211/phy1/ath5k/debug but does not work. Debug level is always 0 The only way I have found if by inserting the module with debug option... Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 30.201426] ath0: Inserted STA 00:27:22:92:d2:50 Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 30.281303] ath0: moving STA 00:27:22:92:d2:50 to state 4 Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 30.352606] ath5k: phy0: (ath5k_ani_calibration:497): listen 905 (now 905) Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 30.352630] ath5k: phy0: (ath5k_ani_calibration:500): check high ofdm 74/452 cck 217/181ath5k: phy0: (ath5k_ani_raise_immunity:229): raise immunity (CCK) Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 31.376814] ath5k: phy0: (ath5k_ani_calibration:497): listen 962 (now 962) Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 31.376838] ath5k: phy0: (ath5k_ani_calibration:500): check high ofdm 56/481 cck 120/192ath5k: phy0: (ath5k_ani_calibration:513): check low ofdm 56/192 cck 120/96 Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 31.67] ath5k: phy0: (ath5k_intr:2190): status 0x1/0x800914b5 Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 31.67] ath5k: phy0: (ath5k_intr:2190): status 0x15/0x800914b5 Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 31.889680] ath5k: phy0: (ath5k_beacon_setup:1724): skb ce916180 [data cee3af8e len 119] skbaddr ee3af8e Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 31.889711] ath5k: phy0: (ath5k_beacon_send:1915): TXDP[9] = e853e00 (ce853e00) Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 31.891178] ath5k: phy0: (ath5k_intr:2190): status 0x1/0x800914b5 Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 31.903552] ath5k: phy0: (ath5k_intr:2190): status 0x4/0x800914b5 Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 32.387031] ath5k: phy0: (ath5k_ani_calibration:497): listen 939 (now 939) Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 32.387079] ath5k: phy0: (ath5k_ani_calibration:513): check low ofdm 46/187 cck 179/93 Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 33.406687] ath5k: phy0: (ath5k_ani_calibration:497): listen 948 (now 948) Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 33.406714] ath5k: phy0: (ath5k_ani_calibration:500): check high ofdm 40/474 cck 110/189ath5k: phy0: (ath5k_ani_calibration:513): check low ofdm 40/189 cck 110/94 Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 34.418685] ath5k: phy0: (ath5k_ani_calibration:497): listen 962 (now 962) Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 34.418740] ath5k: phy0: (ath5k_ani_calibration:513): check low ofdm 37/192 cck 98/96 Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 35.442495] ath5k: phy0: (ath5k_ani_calibration:497): listen 959 (now 959) Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 35.442522] ath5k: phy0: (ath5k_ani_calibration:500): check high ofdm 44/479 cck 78/191ath5k: phy0: (ath5k_ani_calibration:513): check low ofdm 44/191 cck 78/95 Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 35.442561] ath5k: phy0: (ath5k_ani_lower_immunity:314): lower immunityath5k: phy0: (ath5k_ani_set_firstep_level:148): new level 1 Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 36.471835] ath5k: phy0: (ath5k_ani_calibration:497): listen 942 (now 942) Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 36.471859] ath5k: phy0: (ath5k_ani_calibration:500): check high ofdm 72/471 cck 170/188ath5k: phy0: (ath5k_ani_calibration:513): check low ofdm 72/188 cck 170/94 Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 36.897353] ath5k: phy0: (ath5k_intr:2190): status 0x4/0x800914b5 Oct 1 21:16:24 swb-sbw-p2p-gua-new kernel: [ 36.969753] ath5k: phy0: (ath5k_intr:2190): status 0x1/0x800914b5 Oct 1 21:16:25 swb-sbw-p2p-gua-new kernel: [ 37.389197] ath5k: phy0: (ath5k_hw_rf511x_iq_calibrate:1787): I/Q calibration still running Oct 1 21:16:25 swb-sbw-p2p-gua-new kernel: [ 37.389221] ath5k: phy0: (ath5k_hw_phy_calibrate:1869): No I/Q correction performed (2417MHz) Oct 1 21:16:25 swb-sbw-p2p-gua-new kernel: [ 37.490291] ath5k: phy0: (ath5k_ani_calibration:497): listen 965 (now 965) Oct 1 21:16:25 swb-sbw-p2p-gua-new
[ath5k-devel] Clients will mostly not associate on 2.4GHz on long distance links with Compex cards
Hello I've several problems with ath5k. I have used madwifi about 7 years, now I have to switch to ath5k because no madwifi support... If I use ath5k I have some strange issue using master mode. I have upgrade to ath5k and almost all clients in 2.4GHz won't connect. I have on one ap using ath5k 2 different clients using openwrt. Wireless card is a compex WLM54AGP23. It takes a lot of time to one client to connect, others won't connect. An other link in 5.8GHz works fine (but there are other client hw). In labor tests everything is ok, no problems of connecting I have an other ap server with other atheros card WLM54GP23 and the same problem not even clients with madwifi driver are connecting... How can I debug the issue? The signals with madwifi are very good (-60 .. -70). All are long distance links of clients... Distance is set to 25km... On an other link at 5.8GHz with madwifi I have a signal of -66 .. -73 on both sites but with ath5k the client does not connect and on client side I have a signal of -93.. How can I debug this issues? Anyone using this cards for long distance links? Part of hostapd log of one 2.4 Clients which will not connect to server running ath5k Sep 30 11:28:26 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.11: authentication OK (open system) Sep 30 11:28:26 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e MLME: MLME-AUTHENTICATE.indication(00:27:22:e2:6d:8e, OPEN_SYSTEM) Sep 30 11:28:26 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e MLME: MLME-DELETEKEYS.request(00:27:22:e2:6d:8e) Sep 30 11:28:26 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.11: association OK (aid 3) Sep 30 11:28:27 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.11: did not acknowledge authentication response Sep 30 11:28:27 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.11: did not acknowledge association response Sep 30 11:28:37 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e WPA: event 2 notification Sep 30 11:28:37 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.1X: unauthorizing port Sep 30 11:28:37 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.11: disassociated Sep 30 11:28:37 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e MLME: MLME-DISASSOCIATE.indication(00:27:22:e2:6d:8e, 3) Sep 30 11:28:37 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e MLME: MLME-DELETEKEYS.request(00:27:22:e2:6d:8e) Sep 30 14:28:41 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.11: deauthenticated due to inactivity Sep 30 14:28:41 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e MLME: MLME-DEAUTHENTICATE.indication(00:27:22:e2:6d:8e, 2) Sep 30 14:28:41 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e MLME: MLME-DELETEKEYS.request(00:27:22:e2:6d:8e) Sep 30 14:28:43 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.11: authentication OK (open system) Sep 30 14:28:43 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e MLME: MLME-AUTHENTICATE.indication(00:27:22:e2:6d:8e, OPEN_SYSTEM) Sep 30 14:28:43 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e MLME: MLME-DELETEKEYS.request(00:27:22:e2:6d:8e) Sep 30 14:28:43 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.11: association OK (aid 3) Sep 30 14:28:43 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.11: did not acknowledge authentication response Sep 30 14:28:43 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.11: did not acknowledge association response Sep 30 14:28:53 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e WPA: event 2 notification Sep 30 14:28:53 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.1X: unauthorizing port Sep 30 14:28:53 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.11: disassociated Sep 30 14:28:53 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e MLME: MLME-DISASSOCIATE.indication(00:27:22:e2:6d:8e, 3) Sep 30 14:28:53 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e MLME: MLME-DELETEKEYS.request(00:27:22:e2:6d:8e) Sep 30 14:28:53 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e WPA: event 3 notification Sep 30 14:28:53 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.1X: unauthorizing port Sep 30 14:28:53 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.11: deauthenticated Sep 30 14:28:53 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e MLME: MLME-DEAUTHENTICATE.indication(00:27:22:e2:6d:8e, 3) Sep 30 14:28:53 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e MLME: MLME-DELETEKEYS.request(00:27:22:e2:6d:8e) Sep 30 14:28:55 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e IEEE 802.11: authentication OK (open system) Sep 30 14:28:55 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e MLME: MLME-AUTHENTICATE.indication(00:27:22:e2:6d:8e, OPEN_SYSTEM) Sep 30 14:28:55 swb-sbe-p2p-x-new hostapd: ath0: STA 00:27:22:e2:6d:8e
[ath5k-devel] How can I disable ani (Adaptive Noise Immunity) support?
How can I disable ani (Adaptive Noise Immunity) with ath5k? I have not seen anything in /sys/class/ieee80211/phy1 In the past I had problems with madwifi and enabled any... Thanks ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
Re: [ath5k-devel] How can I disable ani (Adaptive Noise Immunity) support?
Ah ok this does the job. Thanks! So it seems to disable you have to use debug version of ath5k ... Greetings On 10/01/2013 11:17 AM, Thomas Hühn wrote: Hi, You can set the ani and all other receiving sensivity values via debugfs: #configuration of ath5k's ANI settings echo ani-off /sys/kernel/debug/ieee80211/phy0/ath5k/ani #highest sensivity echo sens-high /sys/kernel/debug/ieee80211/phy0/ath5k/ani #lowest sensivity #echo sens-low /sys/kernel/debug/ieee80211/phy0/ath5k/ani Just put it in the /etc/rc.local and your system use those at startup. Greetings Thomas On 01.10.2013, at 15:55, Beat Meier mbe...@swiss-wireless.com.ar wrote: How can I disable ani (Adaptive Noise Immunity) with ath5k? I have not seen anything in /sys/class/ieee80211/phy1 In the past I had problems with madwifi and enabled any... Thanks ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
Re: [ath5k-devel] mac80211 and kernel 3.8.13 1/2 speed as with madwifi and kernel 2.6.23 and bad respons time
On 09/18/2013 10:52 AM, Bob Copeland wrote: On Tue, Sep 17, 2013 at 04:33:34PM -0700, Adrian Chadd wrote: ... I think you should start doing some more in-depth system profiling to see where that CPU is actually being used. Saying ksoftirqd is only a little helpful. See if it's handling way too much interrupts, or whether there's lots of card error conditions, or the TX/RX queues are being too frequently checkeed, or ... What I have seen is that with madwifi driver the cpu is 90-100% cpu usage with ksoftirqd with mac80211 about 2% ... Could this be a kernel interrupt issue? Are there several policies which changed with kernel? Indeed I didn't understand at all the stats given above. I took it to mean that madwifi is using much more CPU in the kernel than ath5k, which would be an anti-feature unless ath5k is sleeping too much. At any rate - results of Yes this is what I have seen. If using madwifi driver, iperf is using 10% cpu and almost 80-90% cpu BUT throughput is nice: 13-15Mbps@24M bit rate fix where with ath5k iperf is using 3% cpu and interrupts nothing and throughput is only 5-7Mbps. Hostapd is used with wpa2-psk. perf record [do something wireless] + perf report for both scenarios could shed some light. What do you want to know? On machine where hostap is running: while true; do iperf -c ip_of_sta;done on this machine ksoftirqd/0 use no cpu with top, iperf 1% cpu if at5hk driver is used and 80-90% cpu for ksoftirqd/0 and about 10% for iperf if madwifi is used. On machine were wpa_supplicant is running iperf -s top shows about 2-5% cpu of iperf and nothing about ksoftirqd/0 nevertheless if ath5k or madwifi is used. and visa vers on machine where hostap is running: iperf -s top shows about 2-5% cpu of iperf and nothing about ksoftirqd/0 nevertheless if ath5k or madwifi is used. on machine were wpa_supplicant is running while true; do iperf -c ip_of_masterdone on this machine ksoftirqd/0 use no cpu with top, iperf 1% cpu if at5hk driver is used and 80-90% cpu for ksoftirqd/0 and about 10% for iperf if madwifi is used. Nevertheles if machine were wpa_supplicant is running is using madwifi or ath5k driver throughput is 13-15Mbps IF machine where hostap is running use madwifi driver If machine where hostap is running use ath5k driver throughput is 5-7Mbps nevertheles if machine were wpa_supplicant is running is using madwifi or ath5k driver. Other problem what I see is that the signal is normaly -60 and drops out short time to -78 with ath5k with madwifi not ... Is that what you want to known? BTW: I'm now compiling the kernel with debug support for ath5k drivers ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
Re: [ath5k-devel] mac80211 and kernel 3.8.13 1/2 speed as with madwifi and kernel 2.6.23 and bad respons time
It seems that I'm using already minstrel. I have found the following in the kernel configuration file CONFIG_MAC80211=m CONFIG_MAC80211_HAS_RC=y CONFIG_MAC80211_RC_PID=y CONFIG_MAC80211_RC_MINSTREL=y CONFIG_MAC80211_RC_MINSTREL_HT=y # CONFIG_MAC80211_RC_DEFAULT_PID is not set CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y CONFIG_MAC80211_RC_DEFAULT=minstrel_ht CONFIG_MAC80211_MESH=y CONFIG_MAC80211_LEDS=y # CONFIG_MAC80211_DEBUGFS is not set # CONFIG_MAC80211_MESSAGE_TRACING is not set # CONFIG_MAC80211_DEBUG_MENU is not set I have not found in the wireless documentation how to enable other algo? Is there a module parameter for MAC80211 ? On 09/17/2013 12:32 PM, Yeoh Chun-Yeow wrote: What is the rate control algorithm used by your mac80211? Try use minstrel perhaps. On Sep 17, 2013 7:52 AM, Bob Copeland m...@bobcopeland.com mailto:m...@bobcopeland.com wrote: On Tue, Sep 17, 2013 at 11:27:13AM -0300, Beat Meier wrote: Anyone having same issue? I realy have to switch to this driver because madwifi not anymore supported and I have serveral bad issues but with this throughput impossible to use for me How can I help to debug the problem? I don't see anything like this, but I can't recall the last time I had madwifi working either. A capture of both scenarios would help. -- Bob Copeland %% www.bobcopeland.com http://www.bobcopeland.com ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org mailto:ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
[ath5k-devel] Country settings no honored
Hello I try to enable channel 12 and 13 for reg domain AR which are allowed here for ath5k and WLM54AGP23 (168c:001b) card. I have enabled this in the regdomain binary and installed it with my public key in /lib/crda. I have also tried orig regdomain... Kernel is 3.0.0, distribution debian-6.0 Country is set with hostapd, because iw reg set does not work... Output is the following [7.453516] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [7.453616] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [7.474621] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [7.498654] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [7.525638] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [7.554621] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.295351] cfg80211: Calling CRDA for country: US [8.297104] ath5k phy0: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61) [8.298572] ath5k :00:0e.0: registered as 'phy1' [8.370951] cfg80211: Regulatory domain changed to country: US [8.371495] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [8.372565] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2700 mBm) [8.377458] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 1700 mBm) [8.379754] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.380534] cfg80211: (549 KHz - 560 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.388459] cfg80211: (565 KHz - 571 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.390220] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 3000 mBm) [9.147424] ath5k phy1: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61) [ 14.488129] cfg80211: Calling CRDA for country: AR [ 14.608818] cfg80211: Regulatory domain changed to country: AR [ 14.618512] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 14.619584] cfg80211: (2402000 KHz - 2494000 KHz @ 4 KHz), (N/A, 3000 mBm) But the channels and power seems to be still from country US which was set at startup because iw phy0 info gives the following output: Wiphy phy0 Band 1: Frequencies: * 2412 MHz [1] (27.0 dBm) * 2417 MHz [2] (27.0 dBm) * 2422 MHz [3] (27.0 dBm) * 2427 MHz [4] (27.0 dBm) * 2432 MHz [5] (27.0 dBm) * 2437 MHz [6] (27.0 dBm) * 2442 MHz [7] (27.0 dBm) * 2447 MHz [8] (27.0 dBm) * 2452 MHz [9] (27.0 dBm) * 2457 MHz [10] (27.0 dBm) * 2462 MHz [11] (27.0 dBm) * 2467 MHz [12] (disabled) * 2472 MHz [13] (disabled) * 2484 MHz [14] (disabled) Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps (short preamble supported) * 5.5 Mbps (short preamble supported) * 11.0 Mbps (short preamble supported) * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps So what's wrong that channels are not set right? With madwifi driver it worked to set the channels at least of JP. If you set country JP with the orig regdomain database it's the same stuff channel 12-14 are not enabled. It's seems that the card or what ever stores the first set country which is per default US at startup... How can I set at startup the country? I created file /etc/modprobe.d/cfg80211.conf with then the output is as follows (first set to JP after that someone set it to US and mi hostapd config has too JP...) Waiting for /dev to be fully populated...[7.370263] cfg80211: World regulatory domain updated: [7.376450] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [7.377540] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [7.422579] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [7.439165] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [7.448689] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [7.470357] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [7.477181] cfg80211: Calling CRDA for country: JP [7.653563] cfg80211: Regulatory domain changed to country: JP
Re: [ath5k-devel] How can I rename wlanX to athX ?
On 05/12/2012 07:13 PM, Albert Gall wrote: On Sat, May 12, 2012 at 12:18:30PM -0300, Beat Meier wrote: Hello Is it not possible to name the interface other than wlanX? I want to use compatibility with cacti etc. to use either madwifi or mac802011 and try to use athX instead of wlanX with mac80211 drivers... Thanks Beat ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel Hi, you cant use # ip link set name wlan0 dev ath0 Thanks with your info I have found that ip link set wlan0 name ath0 To auto generate ath0 you can do something like the following in /etc/network/interfaces auto wlan0 iface wlan0 inet static address 10.99.99.1 ### not realy used but must be here for config reasons netmask 255.255.255.0 pre-up ip link set wlan0 name ath0 auto ath0 iface ath0 inet static address 10.24.5.1 netmask 255.255.255.0 hostapd /etc/hostapd/hostapd.ath0.conf Thanks and greetings Beat ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
[ath5k-devel] How can I rename wlanX to athX ?
Hello Is it not possible to name the interface other than wlanX? I want to use compatibility with cacti etc. to use either madwifi or mac802011 and try to use athX instead of wlanX with mac80211 drivers... Thanks Beat ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
[ath5k-devel] ath5k driver not reporting noise floor?
Hello I've used for years madwifi driver and want now switch to ath5k driver. 1. I have noticed that nor iw nor iwconfig using ath5k does report noise floor. Is this not supported with athk5 or does the 80211 spec this not include? 2. Is it possible to rename the interface instead of wlan0, wlan1 etc. to ath0, ath1 to be compatible with madwifi scripts? 3. Last but not least is there nor user list only the devel list? Thanks a lot Beat ___ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
