Skip to contentSkip to conversation

IBSS mode is now supported by CT firmware.

DISCUSSION Ben Greear 5 participants 16 messages Nov 26, 2014 – Dec 4, 2014 Qualcomm Atheros ATH10K wireless driver

lore
Share & tools
lore

Ben Greear

author
#0 lore raw

A company that wishes to remain anonymous is sponsoring my effort to add IBSS (ADHOC) support to my 10.1.467 CT firmware.

The kernel driver must be patched to enable IBSS mode when CT firmware is detected.

The firmware was improved by copying some of the missing IBSS code from the 999.x firmware branch.

I still cannot get WPA2 encryption to work, but open authentication seems to work fine. I still have a good bit more testing to do. I cannot get ath9k to do encryption in IBSS mode either, so I probably am mis-configuring something.

If someone wants to try this out, please download the appropriate firmware binary from here:

http://www.candelatech.com/downloads/ath10k-fw-beta/

Either hack your own kernel, or grab my latest 3.17 kernel:

git clone git://dmz2.candelatech.com/linux-3.17.dev.y

I'm interested to know results if someone tries it out.

Thanks,
Ben

Signature · 8 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#1 lore raw
Quoted 3 lines · Ben Greear

A company that wishes to remain anonymous is sponsoring my effort to add IBSS (ADHOC) support to my 10.1.467 CT firmware.

Great!

Quoted 3 lines

The kernel driver must be patched to enable IBSS mode when CT firmware is detected.

Where can I find the patches?

---
ChunYeow

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

author
#2 lore raw
Quoted 5 lines · Yeoh Chun-Yeow
Quoted 3 lines · Ben Greear

A company that wishes to remain anonymous is sponsoring my effort to add IBSS (ADHOC) support to my 10.1.467 CT firmware.

Quoted 7 lines

Great!

Quoted 3 lines

The kernel driver must be patched to enable IBSS mode when CT firmware is detected.

Where can I find the patches?

My 3.17 kernel:

git clone git://dmz2.candelatech.com/linux-3.17.dev.y

or, browse gitweb:

http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.17.dev.y/.git;a=summary

I'll also backport to my 3.14 tree when I get a chance, but it is not done yet.

Probably not worth trying to post for upstream inclusion since it needs the CT feature flag...

Thanks,
Ben

Signature · 8 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#3 lore raw

Is this the only patch we need to enable IBSS mode?
http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.17.dev.y/.git;a=commit;h=af9dabe5f23e2ad8f8603a5156ebe9227340e9e3

Please advice. Thanks

----
ChunYeow

Quoted 29 lines · Ben Greear
Quoted 5 lines · Yeoh Chun-Yeow
Quoted 3 lines · Ben Greear

A company that wishes to remain anonymous is sponsoring my effort to add IBSS (ADHOC) support to my 10.1.467 CT firmware.

Quoted 7 lines

Great!

Quoted 3 lines

The kernel driver must be patched to enable IBSS mode when CT firmware is detected.

Where can I find the patches?

My 3.17 kernel:

git clone git://dmz2.candelatech.com/linux-3.17.dev.y

or, browse gitweb:

http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.17.dev.y/.git;a=summary

I'll also backport to my 3.14 tree when I get a chance, but it is not done yet.

Probably not worth trying to post for upstream inclusion since it needs the CT feature flag...

Quoted 8 lines

Thanks,
Ben

--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

author
#4 lore raw
Quoted 4 lines · Yeoh Chun-Yeow

Is this the only patch we need to enable IBSS mode?
http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.17.dev.y/.git;a=commit;h=af9dabe5f23e2ad8f8603a5156ebe9227340e9e3

Please advice. Thanks

Sort of, but that is patching a previous patch of mine that is not upstream.

So, you are going to have to go crawling through the code a bit to find out how to do a similar action in your code base.

Thanks,
Ben

Signature · 8 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#6 lore raw
In reply to Ben Greear
Quoted 2 lines · Ben Greear

A company that wishes to remain anonymous is sponsoring my effort to add IBSS (ADHOC) support to my 10.1.467 CT firmware.

Oh, wonderful. I would love to get babeld running on this stuff on adhoc mode....

Quoted 34 lines

The kernel driver must be patched to enable IBSS mode when CT firmware is detected.

The firmware was improved by copying some of the missing IBSS code from the 999.x firmware branch.

I still cannot get WPA2 encryption to work, but open authentication seems to work fine. I still have a good bit more testing to do. I cannot get ath9k to do encryption in IBSS mode either, so I probably am mis-configuring something.

If someone wants to try this out, please download the appropriate firmware binary from here:

http://www.candelatech.com/downloads/ath10k-fw-beta/

Either hack your own kernel, or grab my latest 3.17 kernel:

git clone git://dmz2.candelatech.com/linux-3.17.dev.y

I'm interested to know results if someone tries it out.

Thanks,
Ben

--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

Signature · 8 lines
Dave Täht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#5 lore raw
In reply to Ben Greear

Ok. Thanks. Will take a try on this later.

---
ChunYeow

Quoted 11 lines · Ben Greear
Quoted 4 lines · Yeoh Chun-Yeow

Is this the only patch we need to enable IBSS mode?
http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.17.dev.y/.git;a=commit;h=af9dabe5f23e2ad8f8603a5156ebe9227340e9e3

Please advice. Thanks

Sort of, but that is patching a previous patch of mine that is not upstream.

So, you are going to have to go crawling through the code a bit to find out how to do a similar action in your code base.

Quoted 8 lines

Thanks,
Ben

--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#7 lore raw
In reply to Ben Greear
Quoted 4 lines · Ben Greear

I still cannot get WPA2 encryption to work, but open authentication seems to work fine. I still have a good bit more testing to do. I cannot get ath9k to do encryption in IBSS mode either, so I probably am mis-configuring something.

I don't believe WPA2 is supported with adhoc (at least through wpa_supplicant). However, WPA should be and while testing your firmware, I found that it doesn't seem to work (They don't see each other and thus don't associate).

I also found that, like the 999.x firmware, the rate's do not go higher than 54mbit/s. Is this due to the firmware not advertising proper rates or..?

As for throughput, I get 22mbps TCP, 27.6mbps UDP with no encryption.

- Pushpal

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#8 lore raw
Quoted 6 lines · Pushpal Sidhu
Quoted 4 lines · Ben Greear

I still cannot get WPA2 encryption to work, but open authentication seems to work fine. I still have a good bit more testing to do. I cannot get ath9k to do encryption in IBSS mode either, so I probably am mis-configuring something.

Quoted 8 lines

I don't believe WPA2 is supported with adhoc (at least through wpa_supplicant). However, WPA should be and while testing your firmware, I found that it doesn't seem to work (They don't see each other and thus don't associate).

I also found that, like the 999.x firmware, the rate's do not go higher than 54mbit/s. Is this due to the firmware not advertising proper rates or..?

Are you joining the adhoc network in non-HT mode? Anyway, even if you use HT mode, the rate control is not working for 999.x firmware and always stuck at 6Mbps as far as I know.

-----
Chun-Yeow

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#9 lore raw

For CT firmware, IBSS mode works, but again the Rate Control in HT20 mode is not working at all. It always stuck with 6Mbps Tx Rate.

[  196.030000] ath10k_pci 0000:00:00.0: rx skb 869a5840 len 116 peer

04:f0:21:0c:a5:44 ucast sn 95 rate_idx 0 vht_nss 0 freq 5180 band 1 flag 0x200000 fcs-err 0 mic-err 0 amsdu-more 0

For legacy mode, rate control works. rate_idx to 7 or 54Mbps.

[  156.070000] ath10k_pci 0000:00:00.0: rx skb 86af0900 len 116 peer

04:f0:21:0c:a5:1c ucast sn 95 rate_idx 7 vht_nss 0 freq 5180 band 1 flag 0x200000 fcs-err 0 mic-err 0 amsdu-more 0

Similar to 636 firmware.

----
ChunYeow

Quoted 16 lines · Yeoh Chun-Yeow
Quoted 6 lines · Pushpal Sidhu
Quoted 4 lines · Ben Greear

I still cannot get WPA2 encryption to work, but open authentication seems to work fine. I still have a good bit more testing to do. I cannot get ath9k to do encryption in IBSS mode either, so I probably am mis-configuring something.

Quoted 8 lines

I don't believe WPA2 is supported with adhoc (at least through wpa_supplicant). However, WPA should be and while testing your firmware, I found that it doesn't seem to work (They don't see each other and thus don't associate).

I also found that, like the 999.x firmware, the rate's do not go higher than 54mbit/s. Is this due to the firmware not advertising proper rates or..?

Quoted 6 lines

Are you joining the adhoc network in non-HT mode? Anyway, even if you use HT mode, the rate control is not working for 999.x firmware and always stuck at 6Mbps as far as I know.

-----
Chun-Yeow

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

author
#10 lore raw

I'll investigate the rate-control logic. I don't know enough about IBSS currently to know why it would use different rate-ctrl logic than the normal sta/ap, but hopefully I can figure it out.

Can you post some details on how you configure HT20 v/s legacy mode for IBSS interfaces?

Do you have any reason to believe the problem is in the driver or mac80211 stack, or is this all a firmware issue?

And, if anyone has a different /AC NIC that can do IBSS, I'm curious if ath10k will receive at higher speeds?

Thanks,
Ben

Quoted 47 lines · Yeoh Chun-Yeow

For CT firmware, IBSS mode works, but again the Rate Control in HT20 mode is not working at all. It always stuck with 6Mbps Tx Rate.

[  196.030000] ath10k_pci 0000:00:00.0: rx skb 869a5840 len 116 peer

04:f0:21:0c:a5:44 ucast sn 95 rate_idx 0 vht_nss 0 freq 5180 band 1 flag 0x200000 fcs-err 0 mic-err 0 amsdu-more 0

For legacy mode, rate control works. rate_idx to 7 or 54Mbps.

[  156.070000] ath10k_pci 0000:00:00.0: rx skb 86af0900 len 116 peer

04:f0:21:0c:a5:1c ucast sn 95 rate_idx 7 vht_nss 0 freq 5180 band 1 flag 0x200000 fcs-err 0 mic-err 0 amsdu-more 0

Similar to 636 firmware.

----
ChunYeow

Quoted 16 lines · Yeoh Chun-Yeow
Quoted 6 lines · Pushpal Sidhu
Quoted 4 lines · Ben Greear

I still cannot get WPA2 encryption to work, but open authentication seems to work fine. I still have a good bit more testing to do. I cannot get ath9k to do encryption in IBSS mode either, so I probably am mis-configuring something.

Quoted 8 lines

I don't believe WPA2 is supported with adhoc (at least through wpa_supplicant). However, WPA should be and while testing your firmware, I found that it doesn't seem to work (They don't see each other and thus don't associate).

I also found that, like the 999.x firmware, the rate's do not go higher than 54mbit/s. Is this due to the firmware not advertising proper rates or..?

Quoted 6 lines

Are you joining the adhoc network in non-HT mode? Anyway, even if you use HT mode, the rate control is not working for 999.x firmware and always stuck at 6Mbps as far as I know.

-----
Chun-Yeow

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

Signature · 7 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#11 lore raw
Quoted 6 lines · Ben Greear

I'll investigate the rate-control logic. I don't know enough about IBSS currently to know why it would use different rate-ctrl logic than the normal sta/ap, but hopefully I can figure it out.

Can you post some details on how you configure HT20 v/s legacy mode for IBSS interfaces?

Alright, this is how I configure adhoc mode.

HT20 Mode:
iw phy0 interface add wlan0 type adhoc
ifconfig wlan0 1.1.1.1 netmask 255.255.255.0
iw wlan0 ibss join adhocnet 5180 HT20

Legacy Mode:
iw phy0 interface add wlan0 type adhoc
ifconfig wlan0 1.1.1.1 netmask 255.255.255.0
iw wlan0 ibss join adhocnet 5180

By the way, the peer in ath10k is up in legacy mode first before updating the rate to HT20, triggered by drv_sta_rc_update in net/mac80211/ibss.c.

Is EEE80211_RC_SUPP_RATES_CHANGED working correctly for ath10k?

Quoted 4 lines

Do you have any reason to believe the problem is in the driver or mac80211 stack, or is this all a firmware issue?

Rate control is implemented in firmware, right? So it should be firmware issue unless we intended to use the rate control implemented in mac80211 (minstrel).

By the way, I haven't done the testing on CT firmware. But as far as I know, for 363 firmware, the setting of higher fixed TX rate is possible if you configure HT20, such as follow:

iw wlanX set bitrates legacy-5 ht-mcs-5 3 vht-mcs-5 will setup HT, nss=1, mcs=3

So I think that rate control logic in firmware is not working properly in IBSS mode.

Quoted 3 lines

And, if anyone has a different /AC NIC that can do IBSS, I'm curious if ath10k will receive at higher speeds?

ath9k but the rate control is managed by mac80211.

----
ChunYeow

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#15 lore raw
In reply to Yeoh Chun-Yeow
Quoted 3 lines · Yeoh Chun-Yeow

Are you joining the adhoc network in non-HT mode? Anyway, even if you use HT mode, the rate control is not working for 999.x firmware and always stuck at 6Mbps as far as I know.

Right, I should've been more clear. 6mbps rate when using any HT mdoe (HT20/HT40+-), 54mbps rate in non-HT. Same behavior as the 999.x firmware.

- Pushpal

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#12 lore raw
In reply to Ben Greear
Quoted 2 lines · Ben Greear

Do you have any reason to believe the problem is in the driver or mac80211 stack, or is this all a firmware issue?

Because the rate control logic is embedded in the firmware (I believe this is the reason why we don't have a nice 'rc_stats' table) seems to point to a firmware issue.

Quoted 2 lines

And, if anyone has a different /AC NIC that can do IBSS, I'm curious if ath10k will receive at higher speeds?

So I just created an adhoc network with an ath9k radio (HT40+) with an ath10k radio (with HT40+) and found that the ath9k stayed at HT40/SGI MCS7. Checking on the ath10k, I found the same rate (150mbps) was being used.

A very interesting note, however, is that realistic transfer rates are 27mbps TCP, 37mbps UDP from ath9k->ath10k. ath10k->ath9k has realistic transfer rates of 4.17mbps TCP, 5.18mbps UDP and rates go back to the 6mbps we see earlier.

- Pushpal

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

author
#13 lore raw
Quoted 14 lines · Pushpal Sidhu
Quoted 2 lines · Ben Greear

Do you have any reason to believe the problem is in the driver or mac80211 stack, or is this all a firmware issue?

Because the rate control logic is embedded in the firmware (I believe this is the reason why we don't have a nice 'rc_stats' table) seems to point to a firmware issue.

Quoted 2 lines

And, if anyone has a different /AC NIC that can do IBSS, I'm curious if ath10k will receive at higher speeds?

So I just created an adhoc network with an ath9k radio (HT40+) with an ath10k radio (with HT40+) and found that the ath9k stayed at HT40/SGI MCS7. Checking on the ath10k, I found the same rate (150mbps) was being used.

Quoted 4 lines

A very interesting note, however, is that realistic transfer rates are 27mbps TCP, 37mbps UDP from ath9k->ath10k. ath10k->ath9k has realistic transfer rates of 4.17mbps TCP, 5.18mbps UDP and rates go back to the 6mbps we see earlier.

It may be a bit before I can get back to working on this effort, but I am reading the email and it will help me when I do have time to work on this again.

If you have time, can you see if you can get encryption working with ath9k to ath9k? I could not get that working, and I am not sure if it is my supplicant setup or if I have some other bugs somewhere...

Please post config files if you do get it working.

And, what is ath9k to ath9k transfer rates?

Thanks,
Ben

Quoted 3 lines

- Pushpal

Signature · 8 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#14 lore raw
Quoted 5 lines · On Monday 01 December 2014 09:57:50 Ben Greear wrote:

If you have time, can you see if you can get encryption working with ath9k to ath9k? I could not get that working, and I am not sure if it is my supplicant setup or if I have some other bugs somewhere...

Please post config files if you do get it working.

My wpa_supplicant config:

ap_scan=2

network={
	mode=1
	scan_ssid=0
	ssid="mesh"
	bssid=02:BA:DE:AF:FE:01
	key_mgmt=WPA-PSK
	proto=RSN
	frequency=2462
	fixed_freq=1
	beacon_int=100
	mcast_rate=18
	ibss_ht_mode=HT20
	psk="89b8e7e66900dd31b4d1fefa60ed3efb"
}

You need at least the wpa_supplicant version from
http://w1.fi/cgit/hostap/commit/?id=13adc57b39091dc59372efbeb614b74310dd2e02

Quoted 1 line

And, what is ath9k to ath9k transfer rates?

I don't have numbers here which I am allowed to post but it is only slightly (really tiny difference when measurable at all) slower than the AP<->Sta setup.

But you also need an wpa_supplicant patch to enable HT-rates (together with wpa_supplicant).

http://lists.shmoo.com/pipermail/hostap/2012-November/026934.html

Btw. I haven't tested your fw and thus cannot say if anything written above would also work with ath10k.

Kind regards,
Sven

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k