linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Cedric VONCKEN <cedric.voncken@acksys.fr>,
	ath10k@lists.infradead.org,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: ATH10K VLAN firmware issue
Date: Wed, 09 Dec 2015 07:33:47 -0800	[thread overview]
Message-ID: <566849DB.9040901@candelatech.com> (raw)
In-Reply-To: <773DB8A82AB6A046AE0195C68612A31901C5B293@sbs2003.acksys.local>

This only happens when you use STA  + WDS, or is .1q broken
for you in other cases as well?

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
> eth0.
> 	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.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

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

  reply	other threads:[~2015-12-09 15:33 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 [this message]
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
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=566849DB.9040901@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=cedric.voncken@acksys.fr \
    --cc=linux-wireless@vger.kernel.org \
    /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).