netdev - VLAN ID 0 with priority tagging

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <52E05901.6050601@us.ibm.com>
Date:	Wed, 22 Jan 2014 15:49:21 -0800
From:	Sridhar Samudrala <sri@...ibm.com>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: VLAN ID 0 with priority tagging

I am trying to send a packet with VLAN ID 0 and non-zero priority.

The VLAN interfaces are created on 2 hosts using
     ip link add link eth1 eth1.0 type vlan id 0 egress-qos-map 0:2

When i try to send a packet using ping/arping, on the sender side tcpdump
shows that the VLAN tag is added with ID 0 and priority 2.

However, the receiver is receiving the packet with vlan tag stripped.

I am seeing the same behavior with multiple NICs and also with a switch in
between the 2 hosts or with the 2 hosts connected over loopback cable.

It looks as if the driver on the send side is stripping the tag if vlan 
id is 0.
Is this correct behavior or a bug?
Any clues on how to  get priority tagging to work with vlan id 0?

Thanks
Sridhar

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html