Bridging problem in ath10k (STA)

Bridging problem in ath10k (STA)

[Yeoh Chun-Yeow]

Hi, all

I just found out that the bridging is not able to work for STA mode
even for firmware 10.1.467.2-1 if the AP is operating at 80MHz.

But it is working if the AP is operating at 20MHz or 802.11n instead
of 802.11ac. But off course, the STA needs to associate with AP first
before bridging.

Anyone has the similar problem?

----
ChunYeow

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

RE : Bridging problem in ath10k (STA)

[Vu Hai NGUYEN]

>Hi, all

>I just found out that the bridging is not able to work for STA mode
>even for firmware 10.1.467.2-1 if the AP is operating at 80MHz.

>But it is working if the AP is operating at 20MHz or 802.11n instead
>of 802.11ac. But off course, the STA needs to associate with AP first
>before bridging.

>Anyone has the similar problem?

I do have the station with broken firmware in bridge network, the firmware of Ben from CT can fixe it. You can give it a try :D

NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE



_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: RE : Bridging problem in ath10k (STA)

[Yeoh Chun-Yeow]

I have tested with the following CT firmware:
http://www.candelatech.com/downloads/firmware-2-ct-community.bin

But seems not working for STA mode. I am having problem if the AP is
configured as 802.11ac. Is this FW that you mentioned?

----
ChunYeow

On Wed, Jun 4, 2014 at 5:20 PM, Vu Hai NGUYEN
<vh.nguyen@actiasodielec.fr> wrote:
>>Hi, all
>
>>I just found out that the bridging is not able to work for STA mode
>>even for firmware 10.1.467.2-1 if the AP is operating at 80MHz.
>
>>But it is working if the AP is operating at 20MHz or 802.11n instead
>>of 802.11ac. But off course, the STA needs to associate with AP first
>>before bridging.
>
>>Anyone has the similar problem?
>
> I do have the station with broken firmware in bridge network, the firmware of Ben from CT can fixe it. You can give it a try :D
>
> NGUYEN Vu Hai
> Acita-Sodielec
> Route de Mayres - B.P. 9
> 12100 St GEORGES DE LUZENCON
> FRANCE
>
>

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

RE : RE : Bridging problem in ath10k (STA)

[Vu Hai NGUYEN]

>I have tested with the following CT firmware:
>http://www.candelatech.com/downloads/firmware-2-ct-community.bin

>But seems not working for STA mode. I am having problem if the AP is
>configured as 802.11ac. Is this FW that you mentioned?

Yes, I can enter promiscuous mode to set up bridge network (before associated with AP, configured as 802.11ac) with the firmware in your link or this one:
http://www.candelatech.com/downloads/firmware-2-ct-non-commercial.bin

NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE




_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: RE : RE : Bridging problem in ath10k (STA)

[Yeoh Chun-Yeow]

Hmm, redo the testing. The FW is not crashed on STA site, but could
not ping the AP or IP behind the AP once bridging. Only happen if the
AP is operating at 80MHz.

Any idea on what to look for?

----
ChunYeow

On Wed, Jun 4, 2014 at 6:27 PM, Vu Hai NGUYEN
<vh.nguyen@actiasodielec.fr> wrote:
>>I have tested with the following CT firmware:
>>http://www.candelatech.com/downloads/firmware-2-ct-community.bin
>
>>But seems not working for STA mode. I am having problem if the AP is
>>configured as 802.11ac. Is this FW that you mentioned?
>
> Yes, I can enter promiscuous mode to set up bridge network (before associated with AP, configured as 802.11ac) with the firmware in your link or this one:
> http://www.candelatech.com/downloads/firmware-2-ct-non-commercial.bin
>
> NGUYEN Vu Hai
> Acita-Sodielec
> Route de Mayres - B.P. 9
> 12100 St GEORGES DE LUZENCON
> FRANCE
>
>
>

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: RE : RE : Bridging problem in ath10k (STA)

[Michal Kazior]

On 9 June 2014 12:49, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
> Hmm, redo the testing. The FW is not crashed on STA site, but could
> not ping the AP or IP behind the AP once bridging. Only happen if the
> AP is operating at 80MHz.
>
> Any idea on what to look for?

Does this reproduce if you have non-bridged STA connected to an AP
while the STA interface is in promiscuous mode (so that monitor vdev
is running)? If it doesn't reproduce I'd look for AP configuration
issue. Does your AP have wds_sta=1? Does it create wlanX.staY
interfaces when stations connect? (I'm assuming your AP is running
hostapd).


Michał

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: RE : RE : Bridging problem in ath10k (STA)

[Yeoh Chun-Yeow]

> Does this reproduce if you have non-bridged STA connected to an AP
> while the STA interface is in promiscuous mode (so that monitor vdev
> is running)? If it doesn't reproduce I'd look for AP configuration
> issue. Does your AP have wds_sta=1?

Oops, I missed out the wds_sta=1 in my second config file. So it seems
that this solve the problem.

Also, I found out that even if I bridge the wlan interface first
before associate to the AP, the CT firmware does not crashed.

---
ChunYeow

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: RE : RE : Bridging problem in ath10k (STA)

[Kalle Valo]

Yeoh Chun-Yeow <yeohchunyeow@gmail.com> writes:

>> Does this reproduce if you have non-bridged STA connected to an AP
>> while the STA interface is in promiscuous mode (so that monitor vdev
>> is running)? If it doesn't reproduce I'd look for AP configuration
>> issue. Does your AP have wds_sta=1?
>
> Oops, I missed out the wds_sta=1 in my second config file. So it seems
> that this solve the problem.

It would be good if someone could add a section to the wiki how to
configure this:

http://wireless.kernel.org/en/users/Drivers/ath10k/configuration

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: RE : RE : Bridging problem in ath10k (STA)

[Yeoh Chun-Yeow]

Ok, I have added this in the wiki page.

----
ChunYeow

On Tue, Jun 10, 2014 at 3:01 PM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Yeoh Chun-Yeow <yeohchunyeow@gmail.com> writes:
>
>>> Does this reproduce if you have non-bridged STA connected to an AP
>>> while the STA interface is in promiscuous mode (so that monitor vdev
>>> is running)? If it doesn't reproduce I'd look for AP configuration
>>> issue. Does your AP have wds_sta=1?
>>
>> Oops, I missed out the wds_sta=1 in my second config file. So it seems
>> that this solve the problem.
>
> It would be good if someone could add a section to the wiki how to
> configure this:
>
> http://wireless.kernel.org/en/users/Drivers/ath10k/configuration
>
> --
> Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: RE : RE : Bridging problem in ath10k (STA)

[Kalle Valo]

Yeoh Chun-Yeow <yeohchunyeow@gmail.com> writes:

> Ok, I have added this in the wiki page.

Thanks!

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

RE : Bridging problem in ath10k (STA)

[Vu Hai NGUYEN]

I ran into a problem about bridging while doing test with iperf, my system is like this:
PC1 - Device 1 (AP) <= Wifi => Device 2 (STA) - PC2
My AP is set up in 802.11ac VHT 80. My STA is non-bridged and it associated with my AP directly 
on interface wlan0.
If I run iperf in the direction from AP to STA (option -c on PC1 and -s on PC2), every things work fine.
But in the opposite direction (-s on PC1 and -c on PC2), the interface wlan0.sta1 is created on my AP 
during iperf is running and I lost the connection between 2 device, though "iw wlan.sta1 station dump" 
still report the information about connection (rate, txpower, rx bytes (change very very slowly), ...)
I try to ping but not success and iperf stop running. This problem happened only when I run iperf, not
if I ping between PC1 and PC2 and inverse. 
If I delete the "wds_sta=1" in the config file of hostapd this problem is no more occurred. But I wonder
if only this parameter creates effects on this problem cause I have many STA that could associate
to my AP, some of them are bridged, other are non-bridged and I want to keep "wds_sta=1" in my config
file so that bridged STA can connect.
Any one have any ideas about this?
Thank you in advance.
 
NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE

________________________________________
De : Michal Kazior [michal.kazior@tieto.com]
Date d'envoi : lundi 9 juin 2014 13:00
À : Yeoh Chun-Yeow
Cc : Vu Hai NGUYEN; ath10k@lists.infradead.org
Objet : Re: RE : RE : Bridging problem in ath10k (STA)

On 9 June 2014 12:49, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
> Hmm, redo the testing. The FW is not crashed on STA site, but could
> not ping the AP or IP behind the AP once bridging. Only happen if the
> AP is operating at 80MHz.
>
> Any idea on what to look for?

Does this reproduce if you have non-bridged STA connected to an AP
while the STA interface is in promiscuous mode (so that monitor vdev
is running)? If it doesn't reproduce I'd look for AP configuration
issue. Does your AP have wds_sta=1? Does it create wlanX.staY
interfaces when stations connect? (I'm assuming your AP is running
hostapd).


Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: RE : Bridging problem in ath10k (STA)

[Janusz Dziedzic]

On 10 July 2014 08:48, Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> wrote:
> I ran into a problem about bridging while doing test with iperf, my system is like this:
> PC1 - Device 1 (AP) <= Wifi => Device 2 (STA) - PC2
> My AP is set up in 802.11ac VHT 80. My STA is non-bridged and it associated with my AP directly
> on interface wlan0.
> If I run iperf in the direction from AP to STA (option -c on PC1 and -s on PC2), every things work fine.
> But in the opposite direction (-s on PC1 and -c on PC2), the interface wlan0.sta1 is created on my AP
Just guessing, Is wlan0.sta1 added to bridge? If not what if you will
add it manually after created?

> during iperf is running and I lost the connection between 2 device, though "iw wlan.sta1 station dump"
> still report the information about connection (rate, txpower, rx bytes (change very very slowly), ...)
> I try to ping but not success and iperf stop running. This problem happened only when I run iperf, not
> if I ping between PC1 and PC2 and inverse.
> If I delete the "wds_sta=1" in the config file of hostapd this problem is no more occurred. But I wonder
> if only this parameter creates effects on this problem cause I have many STA that could associate
> to my AP, some of them are bridged, other are non-bridged and I want to keep "wds_sta=1" in my config
> file so that bridged STA can connect.
> Any one have any ideas about this?
> Thank you in advance.
>
> NGUYEN Vu Hai
> Acita-Sodielec
> Route de Mayres - B.P. 9
> 12100 St GEORGES DE LUZENCON
> FRANCE
>
> ________________________________________
> De : Michal Kazior [michal.kazior@tieto.com]
> Date d'envoi : lundi 9 juin 2014 13:00
> À : Yeoh Chun-Yeow
> Cc : Vu Hai NGUYEN; ath10k@lists.infradead.org
> Objet : Re: RE : RE : Bridging problem in ath10k (STA)
>
> On 9 June 2014 12:49, Yeoh Chun-Yeow <yeohchunyeow@gmail.com> wrote:
>> Hmm, redo the testing. The FW is not crashed on STA site, but could
>> not ping the AP or IP behind the AP once bridging. Only happen if the
>> AP is operating at 80MHz.
>>
>> Any idea on what to look for?
>
> Does this reproduce if you have non-bridged STA connected to an AP
> while the STA interface is in promiscuous mode (so that monitor vdev
> is running)? If it doesn't reproduce I'd look for AP configuration
> issue. Does your AP have wds_sta=1? Does it create wlanX.staY
> interfaces when stations connect? (I'm assuming your AP is running
> hostapd).
>
>
> Michał
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

RE : RE : Bridging problem in ath10k (STA)

[Vu Hai NGUYEN]

>>>Just guessing, Is wlan0.sta1 added to bridge? If not what if you will
>>>add it manually after created?

>> Sorry I don't really understand your question. My AP has the interface br0 which connects wlan0 and eth0.
>>I should run "iw dev wlan0.sta1 set 4addr on" to add it manually?
>> And can you guess why does Iperf cause the problem? That interface is created only when I run Iperf, not when
>> pinging between two devices cause my STA is non-bridged and it associate on the interface wlan0 of AP.

>try this:
>brctl addif brX wlan0.sta1

Thank you, I did it but the command returns "the interface wlan0.sta1 is already a member of the bridge, can not enslave
it to the bridge br0".  And I still lost the connection between AP and STA (pinging not success).


NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE



_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k