netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* iproute2 invalid argument mpls labels
@ 2017-08-15  8:17 Алексей Болдырев
  2017-08-15 15:06 ` Stephen Hemminger
  0 siblings, 1 reply; 2+ messages in thread
From: Алексей Болдырев @ 2017-08-15  8:17 UTC (permalink / raw)
  To: netdev

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:~# 

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: iproute2 invalid argument mpls labels
  2017-08-15  8:17 iproute2 invalid argument mpls labels Алексей Болдырев
@ 2017-08-15 15:06 ` Stephen Hemminger
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Hemminger @ 2017-08-15 15:06 UTC (permalink / raw)
  To: Алексей Болдырев
  Cc: netdev

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-08-15 15:06 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-08-15  8:17 iproute2 invalid argument mpls labels Алексей Болдырев
2017-08-15 15:06 ` Stephen Hemminger

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