Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ben Jencks <ben@bjencks.net>
Cc: netdev@vger.kernel.org
Subject: Re: `ip addr show' shows maximum of 56 addresses?
Date: Mon, 05 Dec 2011 22:58:40 +0100	[thread overview]
Message-ID: <1323122320.2467.7.camel@edumazet-laptop> (raw)
In-Reply-To: <E46EABF5-E03F-4DF3-82C8-21017B0FD1A7@bjencks.net>

Le lundi 05 décembre 2011 à 16:12 -0500, Ben Jencks a écrit :
> I'm finding that ip addr show will only give me up to 56 addresses:
> 
> $ ip -6 addr show lo
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 
>     inet6 ::1/128 scope host 
>        valid_lft forever preferred_lft forever
> $ for i in `seq 55` ; do sudo ip addr del fd9a:704e:4d65:136d::`printf '%x\n' $i`/128 dev lo ; done
> $ ip addr show lo | grep inet6 | wc -l
> 56
> $ ip addr show lo | grep ' ::1'
>     inet6 ::1/128 scope host 
> $ sudo ip addr add fd9a:704e:4d65:136d::`printf '%x\n' 56`/128 dev lo
> $ ip addr show lo | grep inet6 | wc -l
> 56
> $ ifconfig lo | grep inet6 | wc -l
> 57
> $ ip addr show lo | grep ' ::1'
> <no output>
> 
> It doesn't even help to specify the address explicitly:
> 
> $ ip addr show dev lo to ::1
> <no output>
> 
> (Ubuntu kernel 2.6.32, tested with both distributed and latest git iproute2)
> 
> I searched for this issue, and even looked in the iproute2/ip/ipaddress.c and couldn't find any explicit limits. Is there a maximum netlink message size causing problems?
> 
> Sorry if this question is too user-ish for a dev list, but both linux-net and lartc looked dead.
> 
> Thanks,
> -Ben--

This was fixed two years ago by commit bcd323262a94b14b in 2.6.33
(ipv6: Allow inet6_dump_addr() to handle more than 64 addresses)

  reply	other threads:[~2011-12-05 21:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-05 21:12 `ip addr show' shows maximum of 56 addresses? Ben Jencks
2011-12-05 21:58 ` Eric Dumazet [this message]
     [not found] <1323129923.2887.51.camel@bwh-desktop>
2011-12-06  3:48 ` Ben Hutchings
2011-12-06 13:47   ` Eric Dumazet

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=1323122320.2467.7.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=ben@bjencks.net \
    --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