* `ip addr show' shows maximum of 56 addresses?
@ 2011-12-05 21:12 Ben Jencks
2011-12-05 21:58 ` Eric Dumazet
0 siblings, 1 reply; 4+ messages in thread
From: Ben Jencks @ 2011-12-05 21:12 UTC (permalink / raw)
To: netdev
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: `ip addr show' shows maximum of 56 addresses?
2011-12-05 21:12 `ip addr show' shows maximum of 56 addresses? Ben Jencks
@ 2011-12-05 21:58 ` Eric Dumazet
0 siblings, 0 replies; 4+ messages in thread
From: Eric Dumazet @ 2011-12-05 21:58 UTC (permalink / raw)
To: Ben Jencks; +Cc: netdev
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)
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: `ip addr show' shows maximum of 56 addresses?
2011-12-06 3:48 ` Ben Hutchings
@ 2011-12-06 13:47 ` Eric Dumazet
0 siblings, 0 replies; 4+ messages in thread
From: Eric Dumazet @ 2011-12-06 13:47 UTC (permalink / raw)
To: Ben Hutchings; +Cc: Ben Jencks, netdev
Le mardi 06 décembre 2011 à 03:48 +0000, Ben Hutchings a écrit :
> Seems like a candidate for 2.6.32.y. I don't think it depends on any of
> your other changes for 2.6.33, does it?
Yes, this is a candidate for 2.6.32.y, I see no dependencies.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: `ip addr show' shows maximum of 56 addresses?
[not found] <1323129923.2887.51.camel@bwh-desktop>
@ 2011-12-06 3:48 ` Ben Hutchings
2011-12-06 13:47 ` Eric Dumazet
0 siblings, 1 reply; 4+ messages in thread
From: Ben Hutchings @ 2011-12-06 3:48 UTC (permalink / raw)
To: Eric Dumazet; +Cc: Ben Jencks, netdev
[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]
Eric Dumazet wrote:
> 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)
Seems like a candidate for 2.6.32.y. I don't think it depends on any of
your other changes for 2.6.33, does it?
Ben.
--
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-12-06 13:47 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-12-05 21:12 `ip addr show' shows maximum of 56 addresses? Ben Jencks
2011-12-05 21:58 ` Eric Dumazet
[not found] <1323129923.2887.51.camel@bwh-desktop>
2011-12-06 3:48 ` Ben Hutchings
2011-12-06 13:47 ` Eric Dumazet
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.