[arch-general] ip addr show doesn't show my ipv4 address after update, is this expected behaviour?
Hi, iproute2 just got updated to 3.5.0-1 (previously was 3.4.0-2), because I use [testing]. ip addr show seems to work differently now, showing me my ipv6 assigned address by default rather than my ipv4 address (which was what I previously got when running ip addr show. The man page for ip-address says the command 'displays addresses and their properties', which means it should at least show the ipv4 address as well? I'm wondering whether this is simply an upstream change/bug, since the man page is a bit unclear and a change in behaviour is normally mentioned in man pages (isn't it?). Of course, easy to workaround using ip -4 addr show....
On Mon, Aug 6, 2012 at 2:44 AM, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
Hi, iproute2 just got updated to 3.5.0-1 (previously was 3.4.0-2), because I use [testing].
ip addr show seems to work differently now, showing me my ipv6 assigned address by default rather than my ipv4 address (which was what I previously got when running ip addr show.
The man page for ip-address says the command 'displays addresses and their properties', which means it should at least show the ipv4 address as well?
I'm wondering whether this is simply an upstream change/bug, since the man page is a bit unclear and a change in behaviour is normally mentioned in man pages (isn't it?).
Of course, easy to workaround using ip -4 addr show....
Interesting post. I've been seeing the same thing and having some minor glitches with network problems. The reason I found it strange is I boot with [ ipv6.disable_ipv6=1 ] and my hosts file show [ 127.0.0.1 localhost.localdomain localhost gandalf ] with no ipv6 designation in it. I was working under the assumption it had to do with my switch to, mostly, systemd while still using the old network daemon.
From the wiki on disabling ipv6
Disable functionality Adding ipv6.disable=1 to the kernel line in your bootloader configuration disables the whole ipv6 stack, which is likely what you want if you are experiencing issues. Alternatively, adding ipv6.disable_ipv6=1 instead will keep the ipv6 stack functional, but not assign ipv6 addresses to any of your network devices. dmesg [ 30.959975] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 30.962396] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready journalctl Aug 06 00:19:12 gandalf kernel: e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Aug 06 00:19:12 gandalf kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Aug 06 00:19:12 gandalf kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes read No sign of and IPv4 address being polled. I'm wondering about a bug but possibly in the systemd startup. I realize my network setup doesn't follow the current trends. I don't use dhcp, netcfg, network manager, etc. It's wired only and a static address setup that's served me well for years. Two computers that had no problem transferring files, sharing a printer, email, web browsing, simple startup and shutdown. Now it seems one must learn how to create your own routing tables with iproute2. Yeah that's just a little tacky but two layers of nat later my security concerns don't jive with the rest of the world. PS. I'm not asking for any HAND HOLDING, yeah I screamed, but when the rules change, the rule book should list the changes. I'm aware of some earlier discussions about multiple interfaces needing to use iproute2 but didn't realize it affected a single interface. I had decided to just live with it, but since someone else ask. Myra -- Life's fun when your sick and psychotic!
On 6 August 2012 09:44, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
Hi, iproute2 just got updated to 3.5.0-1 (previously was 3.4.0-2), because I use [testing].
ip addr show seems to work differently now, showing me my ipv6 assigned address by default rather than my ipv4 address (which was what I previously got when running ip addr show.
The man page for ip-address says the command 'displays addresses and their properties', which means it should at least show the ipv4 address as well?
I'm wondering whether this is simply an upstream change/bug, since the man page is a bit unclear and a change in behaviour is normally mentioned in man pages (isn't it?).
Of course, easy to workaround using ip -4 addr show....
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
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.
On 6 August 2012 12:50, Karol Blazewicz <karol.blazewicz@gmail.com> wrote:
$ 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.
Sure that these options works, but the previous behaviour which: 1. was shorter to write 2. allowed to inspect both IPv6 and IPv4 was much better IMO. The man page only adds confusion, as it says: "ip falls back to the default one, usually inet or any" when no family was specified and it cannot be guessed from arguments.
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?
On Mon, Aug 6, 2012 at 8:28 AM, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
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?
About the changes, most of the documentation is ancient. from http://www.policyrouting.org/iproute2.doc.html Obtaining & Compiling IPROUTE2 The ip utility is just one of the utilities in the IPROUTE2 utility package from Alexey. The primary FTP site was located in Russia at ftp://ftp.inr.ac.ru/ip-routing/ but is no longer running. The most complete mirror is located at http://www.linuxgrill.com/anonymous/iproute2/ with the newest OSDL source code located within the http://www.linuxgrill.com/anonymous/iproute2/NEW-OSDL/ directory. We will assume that you have obtained the latest package usually called iproute2-current symlinked to the latest dated version. The version we primarily cover here is the 1999-06-30 version of IPROUTE2. I cloned the git repo for iproute2 and looked at the man page included with the distrubution, this it the top line [ TH IP 8 "17 January 2002" "iproute2" "Linux" ]. Slightly different than the one in the man ip shows. After several hours of reading it appears to be necessary to use the -4 option to read and ipv4 address. It also seems to make a difference whether your hooked up to a system somewhere, say a business or university, or a single home computer nated behind a satellite internet connection with the name resolver parked in Maryland and no knowledge of your home system. This may not be directly to the point about the changes, but leaves you wondering if any body really knows? About my rant from last night. The way I originally set my system up worked but broke gai configuration This is now # /etc/hosts: static lookup table for host names #<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost.localdomain localhost 192.168.0.3 arwen.localdomain arwen 192.168.0.5 gandalf.localdomain gandalf #::1 localhost.localdomain localhost gandalf If you set it up this way you can talk to each other, but it tends to screw other things up. # /etc/hosts: static lookup table for host names #<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost.localdomain localhost gandalf 192.168.0.3 arwen.localdomain arwen 192.168.0.5 gandalf.localdomain gandalf localhost #::1 localhost.localdomain localhost gandalf My bad. Myra -- Life's fun when your sick and psychotic!
On 08/06/2012 06:07 PM, Myra Nelson wrote: This may be resolved upstream[1]: gene =========== From lkml ====================== I'm re-releasing the iproute2 tools for 3.5.0 kernel. There were a couple of bugs (one serious) in the 3.5.0 version. ... Mike Frysinger (1): Fix regression with 'ip address show' ... =========================================== [1] http://lkml.org/lkml/2012/8/13/236
On Tue, Aug 14, 2012 at 3:20 AM, Genes MailLists <lists@sapience.com> wrote:
On 08/06/2012 06:07 PM, Myra Nelson wrote:
This may be resolved upstream[1]:
gene
=========== From lkml ====================== I'm re-releasing the iproute2 tools for 3.5.0 kernel.
There were a couple of bugs (one serious) in the 3.5.0 version.
...
Mike Frysinger (1): Fix regression with 'ip address show' ... ===========================================
Thanks =) looks like we'll get sane behaviour back soon.
On 13 August 2012 21:20, Genes MailLists <lists@sapience.com> wrote:
On 08/06/2012 06:07 PM, Myra Nelson wrote:
This may be resolved upstream[1]:
gene
=========== From lkml ====================== I'm re-releasing the iproute2 tools for 3.5.0 kernel.
There were a couple of bugs (one serious) in the 3.5.0 version.
...
Mike Frysinger (1): Fix regression with 'ip address show' ... ===========================================
Yep, 3.5.1 works fine.
participants (5)
-
Genes MailLists
-
Karol Blazewicz
-
Lukas Jirkovsky
-
Myra Nelson
-
Oon-Ee Ng