netdev - kernel 4.2 : "bridge vlan" command return empty result (works with kernel 4.1.3)

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]

Date:	Tue, 15 Sep 2015 19:39:22 +0200 (CEST)
From:	Alexandre DERUMIER <aderumier@...so.com>
To:	netdev <netdev@...r.kernel.org>
Cc:	roopa <roopa@...ulusnetworks.com>
Subject: kernel 4.2 : "bridge vlan" command return empty result (works with
 kernel 4.1.3)

Hi,

since kernel 4.2, "bridge vlan" command return empty result.


kernel 4.1.3
------------
# bridge vlan
port	vlan ids
eth0	 1 PVID Egress Untagged
	 90
	 91
	 92
	 93
	 94
	 95
	 96
	 97
	 98
	 99
	 100

vmbr0	 1 PVID Egress Untagged
	 94



kernel 4.2  
----------------
# bridge vlan
port	vlan ids



Note that vlans are correctly working,it seem that is just the display.

tcpdump -e -i vmbr0

19:38:08.005055 00:08:7c:bd:ae:40 (oui Unknown) > 00:18:8b:7c:c8:37 (oui Unknown), ethertype 802.1Q (0x8100), length 64: vlan 94, p 0, ethertype IPv4, 172.20.0.17.52299 > kvmtest2.odiso.net.ssh: Flags [.], ack 339613, win 5523, length 0
19:38:08.007730 00:08:7c:bd:ae:40 (oui Unknown) > 00:18:8b:7c:c8:37 (oui Unknown), ethertype 802.1Q (0x8100), length 64: vlan 94, p 0, ethertype IPv4, 172.20.0.17.52299 > kvmtest2.odiso.net.ssh: Flags [.], ack 342145, win 5568, length 0
19:38:08.010977 00:08:7c:bd:ae:40 (oui Unknown) > 00:18:8b:7c:c8:37 (oui Unknown), ethertype 802.1Q (0x8100), length 64: vlan 94, p 0, ethertype IPv4, 172.20.0.17.52299 > kvmtest2.odiso.net.ssh: Flags [.], ack 344677, win 5614, length 0
19:3
--
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