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.
I'm still having problems getting my WIN2000 guest to network to either the net or, sometimes to the CentOS 5.0 host. I'm running an AMD64 3800 dual core system with 4 GB of RAM.
I've set it up as a NAT network. When they say that the guest and host share the host's IP (static) address, do they mean that they are each set to, say, 192.168.1.3 or do they mean that the guest has it's own static IP address and gets its traffic as a pass-through via the host?
I saw under the CentOS 5.0 Gnome network applet that you can set up static IP forwarding. Do I need to do that?
My guest OS has to be able to reach not only the other machines on my Lan but also the Internet.
I kind of feel as if I just need to find and configure that one last setting and then I'll be golden.
the NAT configuration works like this:
VMWare assigns a private network witch normally is 192.168.x.x/255.255.255.0, where 192.168.x.1 is set for the host and rest of the range will be assigned to the guests, in the guest you should leave it working with DHPC as it will aquire all the necessary configurations automatically.
Being this the case all your guest traffic will be routed trough the host re-writing the sender (guest) ip address with the host real address to allow th info to go out to the network, when a package arrives for the guest the host re-writes, again, the destination ip address to match the guest ip.
In my experience you should work with this configuration only if you've got no other alternative, if you can have another ip address from the network you can use the bridge mode as the host will only pass the packets to and from the network to the host.
Thanks for the input. I tried setting things to DHCP but no go. I even re-set the host and the router to DHCP and shut off the other computers but still no good....after re-booting to make sure the services were restarting.
I think I'm going to have to try re-running the config.pl and set things up as a bridged network and see if that works.
Thanks for the help. I think it's getting me closer to a solution.
vmx files live in your vmware configuartion directory, often ~/.vmware. as stated above, you clearly want bridged networking if possible. ifconfig lives in /sbin/ifconfig. if you can't run it like you did, you're either not root when you run it, or you su'd to root incorrectly... run "su -" then root password, then "ifconfig" will work. you can always just run "/sbin/ifconfig" as any user though.