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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Thx for replying. I'm running Shorewall, but I don't think that's the real cause. Check out my other post:
I've just installed a new ethernet board (via-rhine compatible) as eth2
I also have an rtl8029 at eth0 and a 8139too at eth1. Everything worked fine before installing the new board.. network, services, etc
The problem is that when my system starts up, eth1 appears to be dead.
I start a terminal as root and type:
# ifup eth1
Then eth1 starts working again, but eth2 stops. If I run:
# ifup eth2
Then eth2 starts, and eth1 stops. And so on...
There are no problems with eth0 (connected to a dsl modem)
I don't know either is this a hardware conflict, or a firewall issue (I had always run Shorewall without problems).
Running ifconfig, it seems that eth1 and eth2 are using different IO ports and IRQ numbers.
I have noticed that both via-rhine and 8139too share the same kernel module, named 'mii' ... Does it mean something?
I really don't know what's going on. everything works fine with both boards, but one at the time. Sorry for my bad english.
I *think* "host unreachable" means that there is a dns problem. Try the ping using an ip address. You probably need to check your routing table with "netstat -r". You are trying to ping from this machine to an internal or external computer?
What subnet mask were you using? You may have been trying to define them network. I am not sure what linux would do in that case, or if it is even a problem. I seems like it would definitely cause some routing confusion at least.