Arch Linux

arx

Member

From: 2730ft above sea level

Registered: 2016-04-30

Posts: 46

Unable to ping local vm's

Greetings,

I'm spinning up 2x Centos 7.1 vms via vagrant on my Arch box. The vm's spin up without any errors, I am able to ping out from the vm's as well. The vm's are given local IP's - 192.168.33.4 and 192.168.33.5.

When I try to ping those IP's from my local machine I get a 'time to live exceeded' response with 100% packet loss.

I am using the same process on a Debian box and I don't have this issue.

/etc/hosts and /etc/resolv.conf on my machine and on the vm's are configured appropriately.

Last edited by arx (2017-01-15 06:07:43)

leonshaw

Member

Registered: 2012-01-11

Posts: 19

Re: Unable to ping local vm's

Seems there's a routing loop. Can you check the route table with "ip route" and "ip rule"?

arx

Member

From: 2730ft above sea level

Registered: 2016-04-30

Posts: 46

Re: Unable to ping local vm's

Thanks Leon,

Much thanks for the response!

Scratch that, my previous response must've been an anomaly, laptop vm's stopped, and vm's on this machine started, issue persists.

ip route / ip rule output with both vm's up:

arx@cube ~/godev (dev_env) $ ip route
default via 10.0.0.1 dev enp3s0 src 10.0.0.101 metric 202 
10.0.0.0/24 dev enp3s0 proto kernel scope link src 10.0.0.101 metric 202 
arx@cube ~/godev (dev_env) $ ip rule
0:      from all lookup local 
32766:  from all lookup main 
32767:  from all lookup default 

The difference seems to be that my laptop has

'192.168.33.0/24 dev vboxnet0 proto kernel scope link src 192.168.33.1' for the ip route. It's configured by default when I start the vagrant instance, on debian. Is this not the case for Arch?

Thanks,
-Arx

Thanks,

Last edited by arx (2017-01-15 06:07:18)