Skip to contentSkip to conversation

Trouble connecting to broadcom AC APs?

DISCUSSION Ben Greear 4 participants 12 messages Mar 19, 2014 – Mar 24, 2014 Qualcomm Atheros ATH10K wireless driver

lore
Share & tools
lore

Ben Greear

author
#0 lore raw

We are seeing various funny things when trying to connect ath10k stations to commercial APs with broadcom AC NICs.

It sort of works sometimes, but we often see failure to acquire DHCP lease in a timely manner, etc.

Similar testing on APs using QCA AC NICs appears to work much better.

Our problems could be most anything, including the fact that this testing is done on our modified firmware,
but I am curious if anyone else seems any similar issues?

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 5 lines · Ben Greear

We are seeing various funny things when trying to connect ath10k stations to commercial APs with broadcom AC NICs.

It sort of works sometimes, but we often see failure to acquire DHCP lease in a timely manner, etc.

So it's a problem with broadcast frames? With or without encryption? Did you try disabling power save?

Quoted 6 lines

Similar testing on APs using QCA AC NICs appears to work much better.

Our problems could be most anything, including the fact that this testing is done on our modified firmware, but I am curious if anyone else seems any similar issues?

Occasionally I test connecting to D-Link DIR-865L in STA mode. But I just do just simple ping tests and with manual IPs.

Signature · 6 lines
Kalle Valo

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
author
#2 lore raw
Quoted 10 lines · Kalle Valo
Quoted 5 lines · Ben Greear

We are seeing various funny things when trying to connect ath10k stations to commercial APs with broadcom AC NICs.

It sort of works sometimes, but we often see failure to acquire DHCP lease in a timely manner, etc.

So it's a problem with broadcast frames? With or without encryption? Did you try disabling power save?

With and without encryption we see issues. I am disabling power-save, but from poking around in firmware, I'm not sure how much affect that has.

I'm using commands like this to disable it:
./local/sbin/iw dev sta219 set power_save off

Quoted 9 lines
Quoted 6 lines

Similar testing on APs using QCA AC NICs appears to work much better.

Our problems could be most anything, including the fact that this testing is done on our modified firmware, but I am curious if anyone else seems any similar issues?

Occasionally I test connecting to D-Link DIR-865L in STA mode. But I just do just simple ping tests and with manual IPs.

We'll keep poking at things and see if we can find any pattern or work around.

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

Did the per-rate transmit statistics ever make it into the firmware / driver?

I'd start by looking at what rate(s) it's trying and what the transmit completion statistics say. It could be doing something exceedingly dumb like transmitting on an invalid rate or stream setup.

Same deal with STBC/LDPC. Try disabling those; see what happens.

-a

Quoted 40 lines · Ben Greear
Quoted 10 lines · Kalle Valo
Quoted 5 lines · Ben Greear

We are seeing various funny things when trying to connect ath10k stations to commercial APs with broadcom AC NICs.

It sort of works sometimes, but we often see failure to acquire DHCP lease in a timely manner, etc.

So it's a problem with broadcast frames? With or without encryption? Did you try disabling power save?

With and without encryption we see issues. I am disabling power-save, but from poking around in firmware, I'm not sure how much affect that has.

I'm using commands like this to disable it:
./local/sbin/iw dev sta219 set power_save off

Quoted 9 lines
Quoted 6 lines

Similar testing on APs using QCA AC NICs appears to work much better.

Our problems could be most anything, including the fact that this testing is done on our modified firmware, but I am curious if anyone else seems any similar issues?

Occasionally I test connecting to D-Link DIR-865L in STA mode. But I just do just simple ping tests and with manual IPs.

We'll keep poking at things and see if we can find any pattern or work around.

Thanks,
Ben

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

Quoted 4 lines

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

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

author
#4 lore raw
Quoted 7 lines · Adrian Chadd

Did the per-rate transmit statistics ever make it into the firmware / driver?

I'd start by looking at what rate(s) it's trying and what the transmit completion statistics say. It could be doing something exceedingly dumb like transmitting on an invalid rate or stream setup.

Same deal with STBC/LDPC. Try disabling those; see what happens.

It appears the packets get to the AP, and AP at least tries to respond.

If we bring up stations one at a time instead of multiple at once it works better, and using ddwrt works better than stock firmware on the AP too.

Anyone know how well monitor mode works on ath10k? Would be nice to see what is actually on the air.

Truth is, my main concern now is some issue with tx flush hanging, so it may be a bit until I can dig closely into the issues with the BCM APs.

Thanks,
Ben

Quoted 51 lines

-a

Quoted 44 lines · Ben Greear
Quoted 10 lines · Kalle Valo
Quoted 5 lines · Ben Greear

We are seeing various funny things when trying to connect ath10k stations to commercial APs with broadcom AC NICs.

It sort of works sometimes, but we often see failure to acquire DHCP lease in a timely manner, etc.

So it's a problem with broadcast frames? With or without encryption? Did you try disabling power save?

With and without encryption we see issues. I am disabling power-save, but from poking around in firmware, I'm not sure how much affect that has.

I'm using commands like this to disable it:
./local/sbin/iw dev sta219 set power_save off

Quoted 9 lines
Quoted 6 lines

Similar testing on APs using QCA AC NICs appears to work much better.

Our problems could be most anything, including the fact that this testing is done on our modified firmware, but I am curious if anyone else seems any similar issues?

Occasionally I test connecting to D-Link DIR-865L in STA mode. But I just do just simple ping tests and with manual IPs.

We'll keep poking at things and see if we can find any pattern or work around.

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
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com


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

Is the broadcom ap doing sane or insane things with the sleep bits in transmitted frames?

Is this a problem with 11ac only?

-a

Quoted 79 lines · Ben Greear
Quoted 7 lines · Adrian Chadd

Did the per-rate transmit statistics ever make it into the firmware / driver?

I'd start by looking at what rate(s) it's trying and what the transmit completion statistics say. It could be doing something exceedingly dumb like transmitting on an invalid rate or stream setup.

Same deal with STBC/LDPC. Try disabling those; see what happens.

It appears the packets get to the AP, and AP at least tries to respond.

If we bring up stations one at a time instead of multiple at once it works better, and using ddwrt works better than stock firmware on the AP too.

Anyone know how well monitor mode works on ath10k? Would be nice to see what is actually on the air.

Truth is, my main concern now is some issue with tx flush hanging, so it may be a bit until I can dig closely into the issues with the BCM APs.

Thanks,
Ben

Quoted 51 lines

-a

Quoted 44 lines · Ben Greear
Quoted 10 lines · Kalle Valo
Quoted 5 lines · Ben Greear

We are seeing various funny things when trying to connect ath10k stations to commercial APs with broadcom AC NICs.

It sort of works sometimes, but we often see failure to acquire DHCP lease in a timely manner, etc.

So it's a problem with broadcast frames? With or without encryption? Did you try disabling power save?

With and without encryption we see issues. I am disabling power-save, but from poking around in firmware, I'm not sure how much affect that has.

I'm using commands like this to disable it:
./local/sbin/iw dev sta219 set power_save off

Quoted 9 lines
Quoted 6 lines

Similar testing on APs using QCA AC NICs appears to work much better.

Our problems could be most anything, including the fact that this testing is done on our modified firmware, but I am curious if anyone else seems any similar issues?

Occasionally I test connecting to D-Link DIR-865L in STA mode. But I just do just simple ping tests and with manual IPs.

We'll keep poking at things and see if we can find any pattern or work around.

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

Quoted 4 lines

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

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

author
#6 lore raw
Quoted 4 lines · Adrian Chadd

Is the broadcom ap doing sane or insane things with the sleep bits in transmitted frames?

Is this a problem with 11ac only?

ath9k stations connect just fine, so it's either something with the ath10k (including our modified firmware), or the AP has issues with AC specifically.

Thanks,
Ben

Quoted 95 lines

-a

Quoted 79 lines · Ben Greear
Quoted 7 lines · Adrian Chadd

Did the per-rate transmit statistics ever make it into the firmware / driver?

I'd start by looking at what rate(s) it's trying and what the transmit completion statistics say. It could be doing something exceedingly dumb like transmitting on an invalid rate or stream setup.

Same deal with STBC/LDPC. Try disabling those; see what happens.

It appears the packets get to the AP, and AP at least tries to respond.

If we bring up stations one at a time instead of multiple at once it works better, and using ddwrt works better than stock firmware on the AP too.

Anyone know how well monitor mode works on ath10k? Would be nice to see what is actually on the air.

Truth is, my main concern now is some issue with tx flush hanging, so it may be a bit until I can dig closely into the issues with the BCM APs.

Thanks,
Ben

Quoted 51 lines

-a

Quoted 44 lines · Ben Greear
Quoted 10 lines · Kalle Valo
Quoted 5 lines · Ben Greear

We are seeing various funny things when trying to connect ath10k stations to commercial APs with broadcom AC NICs.

It sort of works sometimes, but we often see failure to acquire DHCP lease in a timely manner, etc.

So it's a problem with broadcast frames? With or without encryption? Did you try disabling power save?

With and without encryption we see issues. I am disabling power-save, but from poking around in firmware, I'm not sure how much affect that has.

I'm using commands like this to disable it:
./local/sbin/iw dev sta219 set power_save off

Quoted 9 lines
Quoted 6 lines

Similar testing on APs using QCA AC NICs appears to work much better.

Our problems could be most anything, including the fact that this testing is done on our modified firmware, but I am curious if anyone else seems any similar issues?

Occasionally I test connecting to D-Link DIR-865L in STA mode. But I just do just simple ping tests and with manual IPs.

We'll keep poking at things and see if we can find any pattern or work around.

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

Quoted 4 lines

--
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
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

.. right, but if you can reproduce it with ath10k in 11n only mode, you can use an existing ath9k sniffer to sniff and see if there's anything fruity in the frames.

-a

Quoted 110 lines · Ben Greear
Quoted 4 lines · Adrian Chadd

Is the broadcom ap doing sane or insane things with the sleep bits in transmitted frames?

Is this a problem with 11ac only?

ath9k stations connect just fine, so it's either something with the ath10k (including our modified firmware), or the AP has issues with AC specifically.

Thanks,
Ben

Quoted 90 lines

-a

Quoted 79 lines · Ben Greear
Quoted 7 lines · Adrian Chadd

Did the per-rate transmit statistics ever make it into the firmware / driver?

I'd start by looking at what rate(s) it's trying and what the transmit completion statistics say. It could be doing something exceedingly dumb like transmitting on an invalid rate or stream setup.

Same deal with STBC/LDPC. Try disabling those; see what happens.

It appears the packets get to the AP, and AP at least tries to respond.

If we bring up stations one at a time instead of multiple at once it works better, and using ddwrt works better than stock firmware on the AP too.

Anyone know how well monitor mode works on ath10k? Would be nice to see what is actually on the air.

Truth is, my main concern now is some issue with tx flush hanging, so it may be a bit until I can dig closely into the issues with the BCM APs.

Thanks,
Ben

Quoted 51 lines

-a

Quoted 44 lines · Ben Greear
Quoted 10 lines · Kalle Valo
Quoted 5 lines · Ben Greear

We are seeing various funny things when trying to connect ath10k stations to commercial APs with broadcom AC NICs.

It sort of works sometimes, but we often see failure to acquire DHCP lease in a timely manner, etc.

So it's a problem with broadcast frames? With or without encryption? Did you try disabling power save?

With and without encryption we see issues. I am disabling power-save, but from poking around in firmware, I'm not sure how much affect that has.

I'm using commands like this to disable it:
./local/sbin/iw dev sta219 set power_save off

Quoted 9 lines
Quoted 6 lines

Similar testing on APs using QCA AC NICs appears to work much better.

Our problems could be most anything, including the fact that this testing is done on our modified firmware, but I am curious if anyone else seems any similar issues?

Occasionally I test connecting to D-Link DIR-865L in STA mode. But I just do just simple ping tests and with manual IPs.

We'll keep poking at things and see if we can find any pattern or work around.

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

Quoted 4 lines

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

Quoted 5 lines

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

Quoted 4 lines

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

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

#8 lore raw
In reply to Ben Greear
Quoted 12 lines · Ben Greear
Quoted 7 lines · Adrian Chadd

Did the per-rate transmit statistics ever make it into the firmware / driver?

I'd start by looking at what rate(s) it's trying and what the transmit completion statistics say. It could be doing something exceedingly dumb like transmitting on an invalid rate or stream setup.

Same deal with STBC/LDPC. Try disabling those; see what happens.

It appears the packets get to the AP, and AP at least tries to respond.

Quoted 7 lines

If we bring up stations one at a time instead of multiple at once it works better, and using ddwrt works better than stock firmware on the AP too.

Anyone know how well monitor mode works on ath10k? Would be nice to see what is actually on the air.

With AP firmware, works fine. Could you send airlogs?

Quoted 65 lines

Truth is, my main concern now is some issue with tx flush hanging, so it may be a bit until I can dig closely into the issues with the BCM APs.

Thanks,
Ben

Quoted 51 lines

-a

Quoted 44 lines · Ben Greear
Quoted 10 lines · Kalle Valo
Quoted 5 lines · Ben Greear

We are seeing various funny things when trying to connect ath10k stations to commercial APs with broadcom AC NICs.

It sort of works sometimes, but we often see failure to acquire DHCP lease in a timely manner, etc.

So it's a problem with broadcast frames? With or without encryption? Did you try disabling power save?

With and without encryption we see issues. I am disabling power-save, but from poking around in firmware, I'm not sure how much affect that has.

I'm using commands like this to disable it:
./local/sbin/iw dev sta219 set power_save off

Quoted 9 lines
Quoted 6 lines

Similar testing on APs using QCA AC NICs appears to work much better.

Our problems could be most anything, including the fact that this testing is done on our modified firmware, but I am curious if anyone else seems any similar issues?

Occasionally I test connecting to D-Link DIR-865L in STA mode. But I just do just simple ping tests and with manual IPs.

We'll keep poking at things and see if we can find any pattern or work around.

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

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

Quoted 4 lines

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

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

#9 lore raw
Quoted 13 lines · Janusz Dziedzic
Quoted 12 lines · Ben Greear
Quoted 7 lines · Adrian Chadd

Did the per-rate transmit statistics ever make it into the firmware / driver?

I'd start by looking at what rate(s) it's trying and what the transmit completion statistics say. It could be doing something exceedingly dumb like transmitting on an invalid rate or stream setup.

Same deal with STBC/LDPC. Try disabling those; see what happens.

It appears the packets get to the AP, and AP at least tries to respond.

Quoted 9 lines
Quoted 7 lines

If we bring up stations one at a time instead of multiple at once it works better, and using ddwrt works better than stock firmware on the AP too.

Anyone know how well monitor mode works on ath10k? Would be nice to see what is actually on the air.

With AP firmware, works fine. Could you send airlogs?

BTW, I have same problem with WRT54G and orginal linksys SW - my home router. Problem disappears when will use FW 636 :)
So, seems AP (389, 467) FW is not the best choice for STA mode.
I suspect PS problem here - but didn't check this yet ...

BR
Janusz

Quoted 65 lines
Quoted 65 lines

Truth is, my main concern now is some issue with tx flush hanging, so it may be a bit until I can dig closely into the issues with the BCM APs.

Thanks,
Ben

Quoted 51 lines

-a

Quoted 44 lines · Ben Greear
Quoted 10 lines · Kalle Valo
Quoted 5 lines · Ben Greear

We are seeing various funny things when trying to connect ath10k stations to commercial APs with broadcom AC NICs.

It sort of works sometimes, but we often see failure to acquire DHCP lease in a timely manner, etc.

So it's a problem with broadcast frames? With or without encryption? Did you try disabling power save?

With and without encryption we see issues. I am disabling power-save, but from poking around in firmware, I'm not sure how much affect that has.

I'm using commands like this to disable it:
./local/sbin/iw dev sta219 set power_save off

Quoted 9 lines
Quoted 6 lines

Similar testing on APs using QCA AC NICs appears to work much better.

Our problems could be most anything, including the fact that this testing is done on our modified firmware, but I am curious if anyone else seems any similar issues?

Occasionally I test connecting to D-Link DIR-865L in STA mode. But I just do just simple ping tests and with manual IPs.

We'll keep poking at things and see if we can find any pattern or work around.

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

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

Quoted 4 lines
Quoted 4 lines

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

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

author
#10 lore raw
Quoted 21 lines · Janusz Dziedzic
Quoted 20 lines · Janusz Dziedzic
Quoted 19 lines · Ben Greear
Quoted 7 lines · Adrian Chadd

Did the per-rate transmit statistics ever make it into the firmware / driver?

I'd start by looking at what rate(s) it's trying and what the transmit completion statistics say. It could be doing something exceedingly dumb like transmitting on an invalid rate or stream setup.

Same deal with STBC/LDPC. Try disabling those; see what happens.

It appears the packets get to the AP, and AP at least tries to respond.

If we bring up stations one at a time instead of multiple at once it works better, and using ddwrt works better than stock firmware on the AP too.

Anyone know how well monitor mode works on ath10k? Would be nice to see what is actually on the air.

Quoted 6 lines
Quoted 2 lines

With AP firmware, works fine. Could you send airlogs?

BTW, I have same problem with WRT54G and orginal linksys SW - my home router. Problem disappears when will use FW 636 :)
So, seems AP (389, 467) FW is not the best choice for STA mode.
I suspect PS problem here - but didn't check this yet ...

Here is another data point...if we make br0 on the AP promisc, then suddenly it works fine.

(we noticed this because starting tcpdump on br0 also 'fixes' the problem).

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
#11 lore raw
Quoted 29 lines · Ben Greear
Quoted 21 lines · Janusz Dziedzic
Quoted 20 lines · Janusz Dziedzic
Quoted 19 lines · Ben Greear
Quoted 7 lines · Adrian Chadd

Did the per-rate transmit statistics ever make it into the firmware / driver?

I'd start by looking at what rate(s) it's trying and what the transmit completion statistics say. It could be doing something exceedingly dumb like transmitting on an invalid rate or stream setup.

Same deal with STBC/LDPC. Try disabling those; see what happens.

It appears the packets get to the AP, and AP at least tries to respond.

If we bring up stations one at a time instead of multiple at once it works better, and using ddwrt works better than stock firmware on the AP too.

Anyone know how well monitor mode works on ath10k? Would be nice to see what is actually on the air.

Quoted 6 lines
Quoted 2 lines

With AP firmware, works fine. Could you send airlogs?

BTW, I have same problem with WRT54G and orginal linksys SW - my home router. Problem disappears when will use FW 636 :)
So, seems AP (389, 467) FW is not the best choice for STA mode.
I suspect PS problem here - but didn't check this yet ...

Quoted 6 lines

Here is another data point...if we make br0 on the AP promisc, then suddenly it works fine.

(we noticed this because starting tcpdump on br0 also 'fixes' the problem).

In my case:

ath10k: ath10k_peer_assoc_h_crypto: rsn ie found
ath10k: ath10k_peer_assoc_h_crypto: wpa ie found
ath10k: mac peer 00:14:bf:16:b8:44 phymode 11g

Next tx don't work because, FW discard this packets for some reason (at least broadcast), I see a lot of:
ath10k: htt tx completion msdu_id 0 discard 1 no_ack 0

while with 636 firmware
ath10k: htt tx completion msdu_id 0 discard 0 no_ack 0

So, could be quite different issue you have. I will check switch to CCMP only while now there is TKIP/CCMP.

BR
Jansuz

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