netdev - Missing iproute2 support for 802.1ad

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>] [day] [month] [year] [list]

Message-ID: <20130620231713.4f6a3c1f@xenia.leun.net>
Date:	Thu, 20 Jun 2013 23:17:13 +0200
From:	Michael Leun <lkml20130126@...ton.leun.net>
To:	kaber@...sh.net, shemminger@...ux-foundation.org
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Missing iproute2 support for 802.1ad



2013-04-19 12:04:31 GMT kaber@...sh.net wrote:

> Add support for 802.1ad VLAN devices. This mainly consists of checking
> for
> ETH_P_8021AD in addition to ETH_P_8021Q in a couple of places and check
> offloading capabilities based on the used protocol.

> Configuration is done using "ip link":

> # ip link add link eth0 eth0.1000 \
> 	type vlan proto 802.1ad id 1000
> # ip link add link eth0.1000 eth0.1000.1000 \
>	type vlan proto 802.1q id 1000

I fear, that does not work:

lara:/home/ml # ip link add link eth0 eth0.1000 type vlan proto 802.1ad id 1000
vlan: what is "proto"?
Usage: ... vlan id VLANID [ FLAG-LIST ]
                          [ ingress-qos-map QOS-MAP ] [ egress-qos-map QOS-MAP ]
[...]

ip does not seem to know about proto. This does not  have changed in
git either.

I've seen there was an patch to add this around somewhen in 2011, but
it does not seem to have made it.

Or did I miss something?

-- 
MfG,

Michael Leun

--
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