From: yu-chieh kung <jay0607@gmail.com>
To: Bruno Antunes <baantunes@gmail.com>
Cc: Mauro Mozzarelli <openwrt@ezplanet.net>,
OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [OpenWrt-Devel] ATH10K VLAN firmware issue
Date: Sat, 5 Nov 2016 01:28:04 +0800 [thread overview]
Message-ID: <CAGJdtRCKidEfDF7sc4BRGSfOTmcGJUJ4KZt0xU1vj4bGAnuu1Q@mail.gmail.com> (raw)
In-Reply-To: <CABUTiXUBfHB5RiZ8=ODzrK4-rCBJZ8QqZuZhMK_J7c7haFMEcw@mail.gmail.com>
I met the same problem before,
if i modify the 1q header to other value (0xaa00) before go into firmware.
I can capture the packet in the air
I think the vlan packet is dropped in firmware.
2016-11-04 22:41 GMT+08:00 Bruno Antunes <baantunes@gmail.com>:
> On 4 November 2016 at 14:18, Mauro Mozzarelli <openwrt@ezplanet.net> wrot=
e:
>> Since the capability is implemented in software you might be testing the
>> limit of your router's CPU i/o speed.
>
> By loading the module in rawmode?
>
> The AP is an APU and Sta is an APU2.
>
>>
>>
>>
>> On 04/11/16 14:13, Bruno Antunes wrote:
>>>
>>> Hi all,
>>>
>>> Old thread but I think the issue is still present.
>>>
>>> I'm running a setup with VLANs with WDS and ath10k cards.
>>>
>>> To make it work both cards must be loaded in rawmode, AP
>>> and Sta, and with no security.
>>>
>>> I'm using a OpenWrt trunk r49941 and the most recent firmware,
>>> 10.2.4.70.58, from Kalle ath10k firmware tree.
>>>
>>> Although it works the throughput is very bad.
>>> Are there any alternatives to improve the throughput.
>>>
>>> Best Regards,
>>> Bruno
>>>
>>> On 9 December 2015 at 17:24, voncken <cedric.voncken@acksys.fr> wrote:
>>>>
>>>>
>>>>> -----Message d'origine-----
>>>>> De : Ben Greear [mailto:greearb@candelatech.com]
>>>>> Envoy=C3=A9 : mercredi 9 d=C3=A9cembre 2015 16:34
>>>>> =C3=80 : Cedric VONCKEN; ath10k@lists.infradead.org; linux-wireless
>>>>> Objet : Re: ATH10K VLAN firmware issue
>>>>>
>>>>> This only happens when you use STA + WDS, or is .1q broken for you i=
n
>>>>> other cases as well?
>>>>
>>>> No, this issue occurs in all modes (STA, STA + WDS, AP).
>>>>
>>>> Thanks
>>>>
>>>> Cedric.
>>>>
>>>>> Thanks,
>>>>> Ben
>>>>>
>>>>> On 12/08/2015 06:29 AM, Cedric VONCKEN wrote:
>>>>>>
>>>>>> I'm testing to transmit frame with 802.1q tag (VLAN).
>>>>>>
>>>>>> My client is set in STA + WDS and the netdev is bridged with et=
h0.
>>>>>> I have a computer with vlan configuration set connected to the =
STA
>>>>>> eth0.
>>>>>>
>>>>>> If I try to transmit frames with 802.1q tag, the frames are not
>>>>
>>>> sent.
>>>>>>
>>>>>> I checked with wireless sniffer, and I don't see the frame with
>>>>>> VLAN
>>>>>> tag (the frames without VLAN tag are sent).
>>>>>>
>>>>>> I tested with firmware 10.2.4.70.14-2 from kale github,
>>>>>> 10.1.467-ct-com-full-015 from candelatech and 10.2.4.70-2 from
>>>>>> openwrt, and in all cases I have the same issue.
>>>>>>
>>>>>> Thanks for your help.
>>>>>>
>>>>>>
>>>>>> --
>>>>>> To unsubscribe from this list: send the line "unsubscribe
>>>>>> linux-wireless" in the body of a message to majordomo@vger.kernel.or=
g
>>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>>>
>>>>> --
>>>>> Ben Greear <greearb@candelatech.com>
>>>>> Candela Technologies Inc http://www.candelatech.com
>>>>
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-wirele=
ss"
>>>> in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>> _______________________________________________
>>> openwrt-devel mailing list
>>> openwrt-devel@lists.openwrt.org
>>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>
>> _______________________________________________
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-11-04 17:28 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 [this message]
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
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=CAGJdtRCKidEfDF7sc4BRGSfOTmcGJUJ4KZt0xU1vj4bGAnuu1Q@mail.gmail.com \
--to=jay0607@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=baantunes@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;
as well as URLs for NNTP newsgroup(s).