Linux systems can't ping each other.

[DJDumlao]

Linux systems can't ping each other on both Virtualbox and GNS3. But can ping any ip address on any router and the routers can ping both Linux vm guest. The nics use are PCnet-Fast III (Am79C973) and using the latest virtualbox software and GNS3, the routing protocol is rip version 2.

192.168.120.101 = Centos
192.168.122.66 = Ubuntu

ATL:

F0/0 = 192.168.1.1/30
F0/1 = 192.168.122.65/25
L0 = 192.168.102.1/25
L1 = 192.168.102.129/25

LAX:

F0/0 = 192.168.1.2/30
F0/1 = 192.168.3.1/30
F3/0 = 192.168.2.1/30
L0 = 192.168.103.1/25
L1 = 192.168.103.129/25

BOS:

F0/0 = 192.168.4.1/30
F0/1 = 192.168.3.2/30
L0 = 192.168.150.193/26
L1 = 192.168.150.129/26


ORD:

F0/0 = 192.168.4.2/30
F0/1 = 192.168.120.1/24
F3/0 = 192.168.2.2/30
L0 = 192.168.101.1/25
L1 = 192.168.101.129/25

[DJDumlao]

Please help me fix the issue, I think its a firewall configuration issue but I might be wrong. Thanks

[DJDumlao]

Also on the third nic which I use to plug into GNS3 I use the generic driver option in order for to connect to gns3. See screen shot. Thanks

[andyp73]

Is there a VirtualBox related question in there somewhere? Judging by the IP addresses you have allocated it looks like the network adapters in the VirtualBox guests are all set to bridged but you should probably confirm that.

It looks like a network configuration issue which puts it into the realms of operating system configuration and support not VirtualBox.

-Andy.

[DJDumlao]

There is no nic card that was set to a bridge option. The only option that was set are:

1.) Nic 1: NAT
2.) Nic 2: Host only adapter
3.) Nic 3: Generic driver

The reason why I open a this topic is because I think it might be a bug on virtualbox because I can telnet and ssh using the host-only adapter ip of the other linux box but I can't ping that ip on the other linux box.

[socratis]

I think it might be a bug on virtualbox because I can telnet and ssh using the host-only adapter ip of the other linux box but I can't ping that ip on the other linux box.

That's not how you get to characterize something as "a bug". You got to be 110% sure that it's a bug.

I'd start with a simpler setup. HostOnly, 2 VMs. Then try to figure out why ICMP is not allowed (mainly firewalls). Then add a 3rd VM to the mix, etc. Then add the rest of your networks.

[DJDumlao]

So I did a different test in which I remove the gns3 part of the equation and just have the two linux vm up. I assume since the virtualbox has a virtual switch on it built it on it, so if its a firewall issue or configuration issue, the result will still fail. But after the test I was able to verify that Ubuntu can ping and telnet into the centos but send centos can't ping and telnet into ubuntu. The error are:

[socratis]

I was able to verify that Ubuntu can ping and telnet into the centos but send centos can't ping and telnet into ubuntu

You need to double check your guest's configuration. I'm afraid it has not that much to do with VirtualBox. In any event, post the results of "ifconfig -a" from both guests, just so we can have a look and give you (maybe) general guidelines...

[DJDumlao]

The two linux vm host-only adapter and nat adapter are set to dhcp. No special rules was set on the vm. Is there a way to upload logs to this forum?

[socratis]

You must have missed the part where I said: Keep it simple. ONE adapter. ONLY. HostOnly.

Logs? What logs? I simply asked for the output of your TCP/IP configuration, you can paste it inline. At this point there are no VBox.log files that need to be viewed. If we need a log, we'll let you know...

[DJDumlao]

After I remove the nat adapter on both linux devices and left only the host-only adapter connected (the 2 vm is powered off when I remove NAT). I receive on both linux devices while trying to ping and telneting to the other device this error: "connect: Network is unreachable", just quick note that both devices can be access via telnet from the host pc. Thanks for the help.

[socratis]

Thanks for the help.

I'm afraid that no help can come, if you keep on not posting the information I asked for:

post the results of "ifconfig -a" from both guests

[DJDumlao]

Here is the info.

Code: Select all

jason@ubuntu-test:~$ sudo su
[sudo] password for jason:
root@ubuntu-test:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 08:00:27:43:f1:f9  
          inet addr:192.168.121.3  Bcast:192.168.121.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe43:f1f9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1180 (1.1 KB)  TX bytes:8599 (8.5 KB)
          Interrupt:16 Base address:0xd240

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:48 errors:0 dropped:0 overruns:0 frame:0
          TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:3712 (3.7 KB)  TX bytes:3712 (3.7 KB)

Code: Select all

[root@centos-test ~]# ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.22.3 netmask 255.255.255.0 broadcast 192.168.22.255
        inet6 fe80::e181:2709:b3e5:84ac prefixlen 64 scopeid ox20<link>
        ether 08:00:27:38:64:fa txqueuelen 1000 (Ethernet)
        RX packets 6 bytes 1006 (1006.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 33 bytes 4852 (4.7 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOoPBACK,RUNNING> mtu 65536
        inet 127.0.0.1 netmask 255.0.0.0
        inet6 ::1 prefixlen 128 scopeid ox10<host>
        loop txqueuelen 1000 (Local Loopback)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 0 bytes 0 (0.0 B)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbro: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
        inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
        ether 52:54:00:1d:1c:a7 txqueuelen 1000 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 0 bytes 0 (0.0 B)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbro-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
        ether 52:54:00:1d:1c:a7 txqueuelen 1000 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 0 bytes 0 (0.0 B)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@centos~test ~]#

[DJDumlao]

route -n output

Code: Select all

jason@ubuntu-test:~$ sudo su
[sudo] password for jason:
root@ubuntu-test:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 etho
192.168.121.0   0.0.0.0         255.255.255.0   U     0      0        0 etho
root@ubuntu-test:~#

Code: Select all

[jason@centos-test ~]$ sudo su
[sudo] password for jason:
Last login: Mon May 14 14:48:10 EDT 2018 on pts/0
[root@centos-test ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.22.0    0.0.0.0         255.255.255.0   U     100    0        0 etho
192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbro
[root@centos-test ~]#

[socratis]

Always prefer text as opposed to image captures. Text is smaller, can be formatted, searchable, quotable.

ubuntu-test:~# ifconfig -a
          inet addr:192.168.121.3  Bcast:192.168.121.255  Mask:255.255.255.0

[root@centos-test ~]# ifconfig -a
          inet 192.168.22.3 netmask 255.255.255.0 broadcast 192.168.22.255

I'm not sure what you're doing, but 1) these are not the default HostOnly IP ranges, 2) these IPs will never talk to one another. By definition! They're not in the same range.

You need to leave your guests to their default settings of DHCP. If you want to assign IPs, netmasks, gateways manually, you need to revisit the basics of networking. I'm afraid that this is turning into a networking 101, and you might have better luck in a more networking-focused forum.