Openstack VM machine internet connectivity issues

asked 2020-08-08 01:29:43 -0500

Bharat90 gravatar image

updated 2020-08-08 21:35:21 -0500

Hi All,

Thank you for the excellent documentation and support. I am successfully able to create VM machines on Openstack cloud.

However, I am facing following Openstack VM machine internet connectivity issues:

1) There is no internet connectivity from Openstack VM machine. 2) ping is successful till Openstack machine (192.168.0.166), but Gateway ip (192.168.0.1) not reachable from Openstack VM machine. 3) No website reachable from Openstack VM machine.

Openstack is installed on Virtualbox VM machine (CentOS 8.2).

Connectivity information: Internet<=====>Router(192.168.0.1)<=====>Oracle VM machine (CentOS 8.2; 192.168.0.166)<=====>Openstack VM Machine (192.168.0.174)

Any help or trigger is much appreciated.

Openstack VM Machine (192.168.0.174) Logs

$ ip route
default via 192.168.0.1 dev eth0
169.254.169.254 via 192.168.0.171 dev eth0
192.168.0.0/24 dev eth0 scope link  src 192.168.0.174
$ ping 192.168.0.166
PING 192.168.0.166 (192.168.0.166): 56 data bytes
64 bytes from 192.168.0.166: seq=0 ttl=64 time=2.657 ms
64 bytes from 192.168.0.166: seq=1 ttl=64 time=1.196 ms
64 bytes from 192.168.0.166: seq=2 ttl=64 time=1.312 ms
64 bytes from 192.168.0.166: seq=3 ttl=64 time=0.875 ms
64 bytes from 192.168.0.166: seq=4 ttl=64 time=0.782 ms
^C
--- 192.168.0.166 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.782/1.364/2.657 ms
$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
^C
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
$ ping google.com
ping: bad address 'google.com'
$
$ sudo cat /etc/resolv.conf
nameserver 192.168.0.1
nameserver 192.168.0.166
nameserver 8.8.8.8
$
$ ip route
default via 192.168.0.1 dev eth0
169.254.169.254 via 192.168.0.171 dev eth0
192.168.0.0/24 dev eth0 scope link  src 192.168.0.174
$
$ ifconfig
eth0      Link encap:Ethernet  HWaddr FA:16:3E:17:F2:F9
          inet addr:192.168.0.174  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::f816:3eff:fe17:f2f9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:572 errors:0 dropped:0 overruns:0 frame:0
          TX packets:571 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:51697 (50.4 KiB)  TX bytes:46506 (45.4 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:35 errors:0 dropped:0 overruns:0 frame:0
          TX packets ...
(more)
edit retag flag offensive close merge delete

Comments

How did you create this cloud? What is the cloud's virtual network structure (it looks like you have only a provider network; not sure)? To what network is the Openstack instance connected? How did the instance get its IP address and resolv.conf content?

Bernd Bausch gravatar imageBernd Bausch ( 2020-08-08 21:41:33 -0500 )edit

I know that you can't normally connect to a VM that runs inside a VirtualBox VM, because VirtualBox doesn't know the nested VM's addresses and blocks access. Perhaps that is your situation, although your case is different: You can't connect from the nested VM.

Bernd Bausch gravatar imageBernd Bausch ( 2020-08-08 21:43:04 -0500 )edit

To understand this better, I would trace traffic, e.g. run tcpdump -i any "ether host FA:16:3E:17:F2:F9 and (arp or icmp)" on the VirtualBox VM and do the equivalent on the VirtualBox host.

My first guess is that VirtualBox blocks access. It's just a guess.

Bernd Bausch gravatar imageBernd Bausch ( 2020-08-08 21:45:54 -0500 )edit