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 new to the Linux world and am having a NIC detection problem with Fedora Core 2. I have two NIC cards in the box, one on the motherboard (which is detected) and on PCI NIC (not detected). typing lspci -v seems to show the PCI NIC, but that is far as I can get with detecting, configuring, etc.
Ok this was the same problem which i had faced long ago and one of my friend helped me out
This is probably because the chipset of your nic is same to the other on also.Because i heard that linux will not load the driver for the same device twice.But in the case of installation it will.But after postinstall probably not.I am assuming that you have realtek chipset in the nic.you can verify by
it will be something like the following
alias eth0 8139too
alias eth1 8139cp
the device eth0 is taking 8139too.that means linux loaded the driver for eth0 first.then only to eth1,which is taking 8139cp.For this i did the following.
I'd try a live CD such as knoppix and see if it autodetects the card. If it does, I'd check to see which module (driver) it choose to use. Assuming the CD has a 2.6 kernel (recent knoppix, for example), try the following command: