Bridging problem in ath10k (STA)

Vu Hai NGUYEN vh.nguyen at actiasodielec.fr
Wed Jul 9 23:48:20 PDT 2014


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 at tieto.com]
Date d'envoi : lundi 9 juin 2014 13:00
À : Yeoh Chun-Yeow
Cc : Vu Hai NGUYEN; ath10k at lists.infradead.org
Objet : Re: RE : RE : Bridging problem in ath10k (STA)

On 9 June 2014 12:49, Yeoh Chun-Yeow <yeohchunyeow at 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ł


More information about the ath10k mailing list