linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Wei Qiang <weiqiang@chinacablecom.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: AR7240 VLAN setup
Date: Wed, 25 Aug 2010 08:59:12 -0700	[thread overview]
Message-ID: <4C753DD0.9040702@candelatech.com> (raw)
In-Reply-To: <B94E9F5324F243B5B714A70B147C8CB1@lenovodbc34d11>

On 08/25/2010 02:13 AM, Wei Qiang wrote:
> *Hi, Ben,*
>
> * *
>
> * Sorry for bother.*
>
> * *
>
> * I have a question about how to setup 802.1Q VLAN on AR7240, and can’t get any answer for days. When I googled “802.1q ar7240”, I noticed that you were the
> supporter of 802.1q module. It seems that you are the only one who may help me resolve the problem now. Support from Atheros is poor.*

You might try the linux wireless mailing list:
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>

I have only messed with VLANs on wired interfaces.

Thanks,
Ben

>
> * *
>
> * The problem itself is quite straight forward: *
>
> * *
>
> *1. All packets to ingress LAN port should have a VLAN tag added, or the tag should be removed at egress LAN port.*
>
> * 2. WAN port will transmit all packets unmodified.*
>
> * *
>
> * If you may have an instruction of how to set AR7240 up, or have some related documents to me, that will be great.*
>
> * *
>
> * I have tried different combinations of those registers, but none of them works.*
>
> * *
>
> * This issue is very important for me, and your help is highly appreciated!*
>
> * *
>
> *Thanks and regards,*
>
> * *
>
> *Wei*
>


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

           reply	other threads:[~2010-08-25 15:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <B94E9F5324F243B5B714A70B147C8CB1@lenovodbc34d11>]

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=4C753DD0.9040702@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=weiqiang@chinacablecom.com \
    /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).