All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eran Mann <emann@mrv.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "David S. Miller" <davem@redhat.com>,
	hadi@cyberus.ca, Bjorn.Andersson@ebc.ericsson.se,
	netdev@oss.sgi.com
Subject: Re: VLAN patches
Date: Mon, 07 Oct 2002 09:09:38 +0200	[thread overview]
Message-ID: <3DA13332.4080109@mrv.com> (raw)
In-Reply-To: 3DA1010A.8020202@candelatech.com

According to 802.1Q (which is BTW available freely from IEEE's site) 
0xFFF VID is "Reserved for implementation use. This VID value shall not 
be configured as a PVID, configured in any Filtering Database entry, 
used in any Management operation, or transmitted in a tag header.".

Regarding the 0 VID it is indeed used for priority-only frames. 
Shouldn't it be supported by alowing the user to configure a priority 
map for the ethernet device (rather than creating another user-visible 
device?

Ben Greear wrote:
> David S. Miller wrote:
>>    From: jamal 
>>       A packet with VLANid 0 and an 802.1p tag > 0 is legal. I
>>    think its known as a "priority tagged" packet (not 100% sure
>>    about the term). Therefore VLANid 0 MUST be accepted and ability to 
>>    send it should be there.
>>
>> Great, I stand corrected, please send me a patch which therefore
>> accepts VID 0 on create and destroy.
 >
> It already accepts on create, you just need to add the patch that
> was already sent to allow for delete.
> 
>>    BTW, what about VLANid 0xFFF?
> 
> I think it is reserved, but my spec is 3 years old, and I don't know
> where it is right now, so whatever it is now, let's not touch it :)

-- 
Eran Mann
Senior Software Engineer
MRV International
Tel: 972-4-9936297
Fax: 972-4-9890430
www.mrv.com

  parent reply	other threads:[~2002-10-07  7:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30  8:23 VLAN patches Andersson Björn
2002-09-30  8:52 ` [VLAN] " Matti Aarnio
2002-09-30 16:02   ` Ben Greear
2002-10-05 19:23 ` Ben Greear
2002-10-06  5:09   ` David S. Miller
2002-10-05 19:27 ` Ben Greear
2002-10-06  4:17   ` David S. Miller
2002-10-06  4:31     ` Ben Greear
2002-10-06  5:05       ` David S. Miller
2002-10-06 22:47         ` jamal
2002-10-07  2:46           ` David S. Miller
2002-10-07  3:35             ` Ben Greear
2002-10-07  5:21               ` David S. Miller
2002-10-07  7:09               ` Eran Mann [this message]
2002-10-07  7:06                 ` David S. Miller
2002-10-07  7:32                   ` Eran Mann
2002-10-07 12:05                 ` jamal
2002-10-07 12:09                   ` David S. Miller
2002-10-07 13:01                 ` Boro King
2002-10-12 22:21     ` Boro King

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=3DA13332.4080109@mrv.com \
    --to=emann@mrv.com \
    --cc=Bjorn.Andersson@ebc.ericsson.se \
    --cc=davem@redhat.com \
    --cc=greearb@candelatech.com \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.