Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So, your VM1 is IP: 192.168.1.3
VM2 is IP: 192.168.1.10
You can ping VM1 from VM2 but not other way around.
In your example, I see you have used the hostnames...
What if you ping with IPs instead? From VM2: ping 192.168.1.3
So, your VM1 is IP: 192.168.1.3
VM2 is IP: 192.168.1.10
You can ping VM1 from VM2 but not other way around.
In your example, I see you have used the hostnames...
What if you ping with IPs instead? From VM2: ping 192.168.1.3
Also check
tracert -n 192.168.1.3
Thanks.
My problem is that VM2 can't see VM3.
VM1 and VM2 can see each other with name and IP.
VM3 IP address is 192.168.1.4.
About the traceroute command:
From VM1 to VM2:
Code:
[root@node1 ~]# traceroute -n 192.168.1.10
traceroute to 192.168.1.10 (192.168.1.10), 30 hops max, 60 byte packets
1 192.168.1.10 3.477 ms !X 3.500 ms !X 2.508 ms !X
From VM1 to VM3:
Code:
[root@node1 ~]# traceroute -n 192.168.1.4
traceroute to 192.168.1.4 (192.168.1.4), 30 hops max, 60 byte packets
1 192.168.1.4 1.682 ms !X 0.519 ms !X 0.326 ms !X
I see... on VM3, can you ping the gateway? If not, double check your network settings...
When I use Internal Network in the VirtualBox, then no need for a gateway! I never defined any gateway. If I must define a gateway and my IP address range is 192.168.1.X, then what is my gateway address? Is 192.168.1.1 my gateway address?
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.0.3.2 0.0.0.0 UG 101 0 0 enp0s8
10.0.3.0 0.0.0.0 255.255.255.0 U 101 0 0 enp0s8
But VMs can see each other? I never defined any “Gateway” and “DNS”. As I said, in the VirtualBox, I selected “Internal Network” in the “Network” section for each virtual machine. Need I any DNS or Gateway address?
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.0.3.2 0.0.0.0 UG 101 0 0 enp0s8
10.0.3.0 0.0.0.0 255.255.255.0 U 101 0 0 enp0s8
But VMs can see each other? I never defined any “Gateway” and “DNS”. As I said, in the VirtualBox, I selected “Internal Network” in the “Network” section for each virtual machine. Need I any DNS or Gateway address?
You have 2 Interfaces above, enp0s3 and enp0s8. Which is Internal network and which is NAT?
In your route table it only has entries for enp0s8. So if you want to communicate over enp0s3 you need to add a route.
You have 2 Interfaces above, enp0s3 and enp0s8. Which is Internal network and which is NAT?
In your route table it only has entries for enp0s8. So if you want to communicate over enp0s3 you need to add a route.
The enp0s3 interface is internal network and enp0s8 is NAT. Can you tell me how can I write a route? The syntax "route add <destination> <gateway> <metric>" need a gateway, but I never defined a gateway!
Why "broadcast 0.0.0.0" ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.