netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Алексей Болдырев" <devel-net-ne-vlezay80@yandex.ru>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: iproute2 invalid argument mpls labels
Date: Tue, 15 Aug 2017 08:06:14 -0700	[thread overview]
Message-ID: <20170815080614.1a6e79ad@xeon-e3> (raw)
In-Reply-To: <77691502785047@web24j.yandex.ru>

On Tue, 15 Aug 2017 11:17:27 +0300
Алексей Болдырев         <devel-net-ne-vlezay80@yandex.ru> wrote:

> I updated the kernel 4.12.6. When the mote is hung on the route more than 8 mpls of marks through iproute2, I get the following:
> 
> root@ne-vlezay80:~# ip route add 10.10.10.0/24 encap mpls 50/60/70/80/90/100/110/120/130 dev lo
> RTNETLINK answers: Invalid argument
> 
> root@ne-vlezay80:~# ip route add 10.10.10.0/24 encap mpls 50/60/70/80/90/100/110/120 dev lo
> root@ne-vlezay80:~#
> 
> root@ne-vlezay80:~# ip r
> default via 10.247.0.1 dev ic-br0 proto zebra metric 20 
> 10.10.10.0/24  encap mpls  ///////120 dev lo scope link 
> 
> root@ne-vlezay80:~# cat /usr/src/linux-4.12.6/net/mpls/internal.h|grep MAX_NEW
> #define MAX_NEW_LABELS 30
> root@ne-vlezay80:~# 
> 
> What is the problem, and how can more than 8 MPLS markers be hung on through iproute2?
> 
> root@ne-vlezay80:~# uname -r
> 4.12.6
> root@ne-vlezay80:~# 

iproute2 just reports what the kernel response is. The invalid argument error 
comes from the kernel.

      reply	other threads:[~2017-08-15 15:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15  8:17 iproute2 invalid argument mpls labels Алексей Болдырев
2017-08-15 15:06 ` Stephen Hemminger [this message]

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=20170815080614.1a6e79ad@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=devel-net-ne-vlezay80@yandex.ru \
    --cc=netdev@vger.kernel.org \
    /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).