Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
Distribution: Slackware, CentOS. Red Hat Enterprise Linux
You are using the VMware NAT interface, so it is going to act just like you put the VM's on different hosts behind a NAT router - they can't see each other. This is because VMware is doing address translation, making it appear that the IP address of the VM is actually the IP address of the host server. For VM's on the same host, VMware is knows the real addresses of each VM and can handle the routing. For VM's on different hosts, they true address of each VM is hidden behind the NAT translator and can't be found.
You either need to use Bridging or Host-Only with routing to the Host-Only subnet.