netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: technique@e-teleport.net
Cc: Kevin Shanahan <kmshanah@disenchant.net>, netdev@vger.kernel.org
Subject: Re: Problem with VLANs and via-velocity driver
Date: Fri, 13 Nov 2009 12:11:18 +0100	[thread overview]
Message-ID: <4AFD3ED6.2040606@trash.net> (raw)
In-Reply-To: <4AFD36C0.3090302@e-teleport.net>

Séguier Régis wrote:
> Patrick McHardy a écrit :
>> Kevin Shanahan wrote:
>>  
>>> I've had some problems with getting a fairly simple (I thought) VLAN
>>> configuration working with the on board Via NICs on my Via M700
>>> board. Looks like as soon as a tagged VLAN interface is added, the
>>> underlying "raw" (untagged) interface stops responding.
>>>
>>>
>> There's some special-casing for VID 0 in velocity_init_cam_filter().
>> Does "ip link add link eth0 type vlan id 0" make any difference?
>> If not, does "ip link set eth0 promisc on"?
>>   
> When we patch the driver to support multiple vlan, we decide to use the
> vlan 0 to desactivate the vlan filtering.

Why? The usual behaviour is to receive both tagged and untagged
frames.

> via-velocity: fix vlan receipt
> 
> - vlans were using a single CAM register (see mac_set_vlan_cam)
> - setting the address filtering registers for vlans is not
>  needed when there is no vlan
> 
> The non-tagged interface is filtered out as soon as a tagged
> (!= 0) interface is created. Its traffic appears again when an
> zero-tagged interface is created.

VID 0 doesn't mean untagged, it means the tag contains only a priority
value.

  reply	other threads:[~2009-11-13 11:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13  3:32 Problem with VLANs and via-velocity driver Kevin Shanahan
2009-11-13  6:40 ` Patrick McHardy
2009-11-13 10:36   ` Séguier Régis
2009-11-13 11:11     ` Patrick McHardy [this message]
2009-11-13 11:40       ` Séguier Régis
2009-11-19 15:17         ` Patrick McHardy
2009-11-16  0:57   ` Kevin Shanahan
2009-11-19 15:18     ` Patrick McHardy
2010-02-10 16:43     ` Tiago Pierezan Camargo
2010-02-10 16:46       ` Patrick McHardy
2010-02-11 16:50         ` Tiago Pierezan Camargo
2010-02-11 16:59           ` Patrick McHardy

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=4AFD3ED6.2040606@trash.net \
    --to=kaber@trash.net \
    --cc=kmshanah@disenchant.net \
    --cc=netdev@vger.kernel.org \
    --cc=technique@e-teleport.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).