lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 02 Feb 2012 13:53:37 +0100
From:	Eric Dumazet <>
To:	Benny Amorsen <>
Cc:	yao zhao <>,
	Leonardo Uzcudun <>,
	"" <>
Subject: Re: VLAN 1 - Native

Le jeudi 02 février 2012 à 13:10 +0100, Benny Amorsen a écrit :
> Eric Dumazet <> writes:
> > There is no ID reserved to untagged traffic in the 802.1Q specs, since
> > by definition, if traffic is untagged, there is _no_ VLAN tag in the
> > frame.
> This is not entirely true. If you want to send 802.1p-tagged packets
> without a specific VLAN, you should use the 0 tag. I would say that
> comes quite close to "The ID reserved to untagged traffic is 0".
> It is, however, not 1.

There is a big confusion on the subject and terminology

_IF_ a 802.1Q Header is present in a frame, VID is a 12 bits field.
In the standard, only 0x000 and 0xFFF are reserved. Not 1.
On linux you can still use the full range, if you really want.

_IF_ no 802.1Q header is present, there is no VLAN id included in the
frame. This is what I called "Untagged"

To send a frame without 802.1Q header on linux, use the undelying
device, eth0.

Dont expect eth0.XXX to send a frame without 802.1Q header, since
eth0.XXX is _requested_ to send a 802.1Q header.

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists