On 6 Aug 2012 18:51, "Karol Blazewicz" <karol.blazewicz@gmail.com> wrote:
On Mon, Aug 6, 2012 at 12:30 PM, Lukas Jirkovsky <l.jirkovsky@gmail.com>
wrote:
I have the same problem, but it doesn't even show the IPv6 address. Only the link address is shown, which is of no use.
iproute2 3.4.0-2: --------------------- 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 20:cf:30:55:81:2d brd ff:ff:ff:ff:ff:ff inet 10.77.116.13/24 brd 10.77.116.255 scope global eth0 inet6 2a01:490:11:7488:22cf:30ff:fe55:812d/64 scope global dynamic valid_lft 2591780sec preferred_lft 604580sec inet6 fe80::22cf:30ff:fe55:812d/64 scope link valid_lft forever preferred_lft forever
iproute2 3.5.0-1 --------------------- 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 20:cf:30:55:81:2d brd ff:ff:ff:ff:ff:ff
$ ip -4 addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN inet 127.0.0.1/8 scope host lo 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0
Read the man page for other options.
My question was when/why/whether this changed. Previously without the -4 flag it would show the ipv4 address, now the flag is necessary. Bug or upstream change?