Arch Linux

404

Member

Registered: 2015-09-12

Posts: 2

[SOLVED] Missing IPv4 addresses

As the title says, I get missing IPv4 addresses on some interfaces (only virtual so far). Saint Google haven't been much helpful.

I first noticed the issue while working with Vagrant being unable to SSH into the virtual instance.

The output from ip address is:

vboxnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
inet6 fe80::800:27ff:fe00:0/64 scope link 
   valid_lft forever preferred_lft forever

Initially thought it was an issue from Vagrant not properly setting up the interface. Going in Virtual Box to Preferences > Network > Host only network I can see that the vboxnet0 interface has an IPv4 address assigned but it's not displayed from ip address (as in the example above).

I can fix it by manually setting the same IPv4 address from Virtual Box preferences:

sudo ip addr add 172.28.33.1/24 dev vboxnet0

I get the following:

vboxnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 172.28.33.1/24 scope global vboxnet0
   valid_lft forever preferred_lft forever
inet6 fe80::800:27ff:fe00:0/64 scope link 
   valid_lft forever preferred_lft forever

After that everything works as expected but the fix is lost after rebooting. Switched to thinking that it was an issue from Virtual Box.

As of today I get the same issue with docker's interface. It used to work just fine, getting the IPv4 address out of the box even when the vboxnet0 interface was "broken".

docker0@NONE: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
link/ether 02:42:2b:85:a0:5c brd ff:ff:ff:ff:ff:ff
inet6 fe80::42:2bff:fe85:a05c/64 scope link 
   valid_lft forever preferred_lft forever

Again, it can be fixed by manually adding the IPv4 address but it gets lost after rebooting.

Having two "broken" network interfaces from different applications it points to being an issue with some network configuration or something else related to the system itself.

I haven't spotted any possible issue related to IPv6 or iptables but networking isn't my strong suit so any help or insights are much appreciated.

Last edited by 404 (2015-09-13 17:37:11)

404

Member

Registered: 2015-09-12

Posts: 2

Re: [SOLVED] Missing IPv4 addresses

I got some good advice from someone that had the same issue and was able to fix it.

Apparently Virtual Box uses ifconfig rather than ip for setting up the network, just installing net-tools solved the issue.

Docker's interface seems to be "fixed" too. Although I experienced the same issue after installing net-tools I wasn't able to reproduce it willingly.