[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20160616.171411.1102610413053475579.davem@davemloft.net>
Date: Thu, 16 Jun 2016 17:14:11 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: simon.horman@...ronome.com
Cc: netdev@...r.kernel.org, rshearma@...cade.com,
roopa@...ulusnetworks.com
Subject: Re: [PATCH net-next] mpls: allow routes on ipgre devices
From: Simon Horman <simon.horman@...ronome.com>
Date: Thu, 16 Jun 2016 17:09:09 +0900
> 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>
> Signed-off-by: Simon Horman <simon.horman@...ronome.com>
Applied, thanks Simon.
Powered by blists - more mailing lists