[arch-general] ip addr show doesn't show my ipv4 address after update, is this expected behaviour?

[Myra Nelson]

On Mon, Aug 6, 2012 at 8:28 AM, Oon-Ee Ng <ngoonee.talk at gmail.com> wrote:
> On 6 Aug 2012 18:51, "Karol Blazewicz" <karol.blazewicz at gmail.com> wrote:
>>
>> On Mon, Aug 6, 2012 at 12:30 PM, Lukas Jirkovsky <l.jirkovsky at 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!