netdev - Re: [PATCH net-next] mpls: allow routes on ipgre devices

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

Date:	Thu, 16 Jun 2016 14:12:47 +0100
From:	Robert Shearman <rshearma@...cade.com>
To:	Simon Horman <simon.horman@...ronome.com>,
	"David S. Miller" <davem@...emloft.net>
CC:	<netdev@...r.kernel.org>, Roopa Prabhu <roopa@...ulusnetworks.com>
Subject: Re: [PATCH net-next] mpls: allow routes on ipgre devices

On 16/06/16 09:09, Simon Horman wrote:
> This appears to be necessary and sufficient to provide
> MPLS in GRE (RFC4023) support.
>
> This can be used by establishing an ipgre tunnel device
> and then routing MPLS over it.
>
> The following example will forward MPLS frames received with an outermost
> MPLS label 100 over tun1, a GRE tunnel. The forwarded packet will have the
> outermost MPLS LSE removed and two new LSEs added with labels 200
> (outermost) and 300 (next).
>
> ip link add name tun1 type gre remote 10.0.99.193 local 10.0.99.192 ttl 225
> ip link set up dev tun1
> ip addr add 10.0.98.192/24 dev tun1
> ip route sh
>
> echo 1 > /proc/sys/net/mpls/conf/eth0/input
> echo 101 > /proc/sys/net/mpls/platform_labels
> ip -f mpls route add 100 as 200/300 via inet 10.0.98.193
> ip -f mpls route sh
>
> Also remove unnecessary braces.
>
> Reviewed-by: Dinan Gunawardena <dinan.gunawardena@...ronome.com>

Thanks for testing this and making the necessary change.

Acked-by: Robert Shearman <rshearma@...cade.com>

> Signed-off-by: Simon Horman <simon.horman@...ronome.com>