ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Bruno Antunes <baantunes@gmail.com>
Cc: Mauro Mozzarelli <openwrt@ezplanet.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	yu-chieh kung <jay0607@gmail.com>
Subject: Re: [OpenWrt-Devel] ATH10K VLAN firmware issue
Date: Mon, 07 Nov 2016 06:06:34 -0800	[thread overview]
Message-ID: <58208A6A.5040307@candelatech.com> (raw)
In-Reply-To: <CABUTiXXvqQ=yrrK3wp0fck=Mcb0LSrE7_Jw6KisYOuADvo3sdQ@mail.gmail.com>

On 11/07/2016 03:54 AM, Bruno Antunes wrote:
> On 4 November 2016 at 22:23, Ben Greear <greearb@candelatech.com> wrote:
>> The bug appears that vlan-tx-stripping is unconditionally enabled in
>> at least my firmware.  I have re-compiled w/out that flag set, and it
>> appears
>> to work for me.
>>
>> Please download this firmware, rename it firmware-2.bin, make sure you
>> remove/rename
>> any firmware-5.bin (etc) so mine will load, and see if that fixes your
>> problem.
>
> Thanks for the fast reply but it only solves "half"  the problem.
>
> Now the connection between the AP and the Sta can be secure and the
> driver doesn't need to be loaded in rawmode.
>
> Unfortunatly the the throughput is still bad.
>
> iperf3 -c 10.10.4.15
> Connecting to host 10.10.4.15, port 5201
> [  4] local 10.10.4.16 port 44893 connected to 10.10.4.15 port 5201
> [ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
> [  4]   0.00-1.01   sec  42.4 KBytes   345 Kbits/sec    6   1.41 KBytes
> [  4]   1.01-2.01   sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes
> [  4]   2.01-3.01   sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes
> [  4]   3.01-4.01   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes
> [  4]   4.01-5.01   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes
> [  4]   5.01-6.01   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes
> [  4]   6.01-7.01   sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes
> [  4]   7.01-8.01   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes
> [  4]   8.01-9.01   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes
> [  4]   9.01-10.01  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes
> - - - - - - - - - - - - - - - - - - - - - - - - -
> [ ID] Interval           Transfer     Bandwidth       Retr
> [  4]   0.00-10.01  sec  42.4 KBytes  34.7 Kbits/sec    9             sender
> [  4]   0.00-10.01  sec  0.00 Bytes  0.00 bits/sec                  receiver

You have a complex setup, so I think it would be best if you could break it into
simpler parts to test.

First, try just STA to AP, no vlans, and see if you get useful throughput.

Then try with VLANs

Then, try with WDS.

Then try with WDS and vlans.

In STA to AP mode with VLANs, it performed well for me.

Thanks,
Ben


>
> iperf Done.
>
>>
>> Please note that it is very likely you will have to use same MAC address
>> for the VLAN devices that the underlying station uses in order for this to
>> work.
>
> Can you please elaborate more?
> My setup  is the folowing.
> The connection between the AP and Sta is in WDS
> For the moment all devices are in the same VLAN.
>
> client1 --- SW1 ---- AP ...... Sta ---- SW2 --- client2
>
>
> Thanks,
> Bruno
>
>>
>> https://www.candelatech.com/downloads/tmp/firmware-2-full-community.bin
>>
>>
>> Thanks,
>> Ben
>>
>>
>>
>
>> Ben Greear <greearb@candelatech.com>
>> Candela Technologies Inc  http://www.candelatech.com
>>
>

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

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

  reply	other threads:[~2016-11-07 14:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 14:29 ATH10K VLAN firmware issue Cedric VONCKEN
2015-12-09 15:33 ` Ben Greear
2015-12-09 17:24   ` voncken
2016-11-04 14:13     ` Bruno Antunes
     [not found]       ` <27f802e7-79c5-a17f-1883-88e62a6520ef@ezplanet.net>
2016-11-04 14:41         ` [OpenWrt-Devel] " Bruno Antunes
2016-11-04 17:28           ` yu-chieh kung
2016-11-04 21:50             ` Ben Greear
2016-11-04 22:23               ` Ben Greear
2016-11-05  8:05                 ` Sebastian Gottschall
2016-11-05 14:35                   ` Ben Greear
2016-11-15 14:37                     ` voncken
2016-11-15 14:55                       ` Ben Greear
2016-11-15 15:00                         ` Bruno Antunes
2016-11-15 15:06                           ` Ben Greear
2016-11-07 11:54                 ` Bruno Antunes
2016-11-07 14:06                   ` Ben Greear [this message]
2016-11-07 14:13                     ` Bruno Antunes
2016-11-04 21:17       ` Valo, Kalle
2016-11-07 12:01         ` Bruno Antunes
2016-11-07 18:06           ` Valo, Kalle
2016-11-07 18:40             ` [OpenWrt-Devel] " Bruno Antunes
2016-11-15 13:43               ` Valo, Kalle
2016-11-15 14:53                 ` Bruno Antunes
2017-02-21 12:59                 ` voncken
2017-02-21 13:19                   ` Valo, Kalle
     [not found]                     ` <CAKR_QVLpSWab-kF-f8=xqw+oWAfA966GDm7CtXrWfzmJz8gP-w@mail.gmail.com>
2017-02-21 16:47                       ` Bruno Antunes
2017-02-22 13:55                     ` voncken

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58208A6A.5040307@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=baantunes@gmail.com \
    --cc=jay0607@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=openwrt@ezplanet.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox