From: Robert Shearman <rshearma@brocade.com>
To: Sam Russell <sam.h.russell@gmail.com>, <netdev@vger.kernel.org>
Subject: Re: MPLS decap with iproute2
Date: Mon, 7 Dec 2015 21:42:50 +0000 [thread overview]
Message-ID: <5665FD5A.8000200@brocade.com> (raw)
In-Reply-To: <CAJm+voVUXPBXBRo98K6XS9pVEkN=fCJ4chRdQ=azcZO9ge9gEg@mail.gmail.com>
On 07/12/15 19:42, Sam Russell wrote:
> Hi,
>
> I've had success with the iproute2 manpage example for encapsulating
> outgoing traffic in MPLS, but I've not found a way to add decap routes
> inbound.
>
> I've tried "ip route -f mpls add 100 dev lo" and other variations, but I
> get netlink errors back.
>
> Has this been built yet? Is there sample config that I can try out? I'm
> running a home-built 4.3 kernel + iproute2 built from head (on ubuntu
> 15.10) and am comfortable with perf and splashing around in the codebase if
> need be.
Hi Sam,
This certainly works on net-next, albeit with a bug on the subsequent
"ip route -f mpls list" that I'll shortly be sending a patch for.
Have you first set an appropriate label table size? E.g.:
$ sysctl net.mpls.platform_labels=1048575
If you intend to receive non-BOS traffic over your route above, then you
should also make sure to enable mpls input on lo (and your actual input
interfaces), otherwise the traffic will be dropped.
Thanks,
Rob
next prev parent reply other threads:[~2015-12-07 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 19:42 MPLS decap with iproute2 Sam Russell
2015-12-07 21:42 ` Robert Shearman [this message]
2015-12-07 21:50 ` Sam Russell
2015-12-08 21:45 ` David Ahern
2015-12-08 2:37 ` roopa
2015-12-08 7:26 ` Sam Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5665FD5A.8000200@brocade.com \
--to=rshearma@brocade.com \
--cc=netdev@vger.kernel.org \
--cc=sam.h.russell@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).