Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Hi,
I have a dual boot machine win98 and Redhat 7.2.My network 8139 runs well on my win98 , but lately i was trying to configure my network card on Redhat 7.2,... I successfully configured the ip address and all the essentials address needed thru linuxconf and thru system/network configuration .Then when I type the command ifup eth0 i get a message ...
8139too seems to be not present.
I dont know why...
when i entered my ip address and other address , the device name shown on the interface was eth0 and interrupt at 3
please find me a solution ..as i really am dying to get into the internet thru linux....
You may need to add a line to your /etc/modules.conf file like the following;
alias eth0 8139too
Before you do that, you can try loading the 8139too module to be sure you've got it. Use "lsmod" to list modules that are loaded, and "modprobe" to load modules with dependencies.
If loading the 8139too module manually corrects the problem with ifconfig, then adding the alias in /etc/modules.conf should make it automatic on reboot.
I have a question similar to this one. Well I guess it's only similar in that I have the same card. Anyway, last night I recompiled my kernel on my HP Kayak machine. It has 2 ethernet cards, one for the internal network, one for the external network (i.e. the internet). So when I restarted after recompiling I got this when the system was trying to bring up eth0:
Determining IP information for eth0...PING 68.13.144.1 (68.13.144.1) 56(84) bytes of data
So I went to X windows (using Red Hat's version of Gnome) and when I started the network configuration tool I got this:
eth0 has an alias to module 8139too in modules.conf, instead of currently loaded module pcnet32!
eth1 has an alias to module pcnet32 in modules.conf, instead of currently loaded module 8139too!
Here is what's in my modules.conf file:
alias eth0 8139too
alias eth1 pcnet32
alias scsi_hostadapter aic7xxx
alias scsi_hostadapter1 sym53c8xxx
alias usb-controller usb-uhci
OK logic would lead me to believe that I just need to switch the aliases around in my modules.conf file and everything should be kewl. Am I right in assuming that or is something deeper at work here.
I've only configured a couple of machines with multiple ethernet adapters. I have always just added the lines to /etc/modules.conf and then tested (by plugging a wire into only one card) to see which card was which (eth0/eth1). I have no idea what order drivers are loaded and how the interfaces are assigned. In your situation, I think I'd swap eth0 and eth1, reboot, and see what happens. You aren't going to hurt anything by doing that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.