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 running VmWare 4.05 (6030) under Windows XP, with 3 vritual machines.
Virtual Machine 1) Windows 2000 + SP4 - running with vmware N.A.T. @ 100%
V M 2) RedHat Linux 9.0 - running with vmware Bridge on eth0 and vmware N.A.T. on eth1 both @100%
V M 3) Fedora Core 1 - running with vmware N.A.T. on eth1 @100% and running with vmware bridge on eth0, with last one not working properly.
I've already tried the fix mentioned on this forum (the one from the vmware manual) and it stops the cable signal problem, but while the N.A.T. device works great with ifup eth1, eth0 just starts trying to get a new IP and after a while it displays this message:
"Determining IP information for eth0... failed."
The bridge protocol is installed on a "real" National Semiconductor DP83815-Based PCI Fast Ethernet Adapter NIC, which is connected to a 3COM Cable Modem.
Has anybody ever experienced this with fedora, because with RH9 it works fine.
BTW, if I check my CM's diagnostic page, the NICs parameters all show up right (even the MAC Address), but the IP shows up as 0.0.0.0 .
PS: I have a felling it has something to do with fedora and vmware 4.05, since fedora isn't officially supported by VmWare.
There is a problem with link checking... it 'thinks' that the link is down... so the solution is that you add the following lines in to /etc/sysconfig/network-scripts/ifcfg-eth0 (if that is your bridge device in host system).