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.
I am connected to my LAN network through eth0, and it worked
fine. After powring off the machine and botting it up later I get this message."Bringing up interface eth0: failed"
Trying "service network restart" I get again the same message.
No changes have been done to my system in between.
Check the files in /var/log. There should be info on why it didn't start. May want to make sure it is loading the modules for the network card too. Mandrake usually makes them modules instead of built into the kernel. It may not be loading them when you reboot. If the modules are not loading, it won't work.
Hope that helps. Need more info at the moment though.
I've had a similar problem and was helped out here. In Mandrake Control Center -> Network & Internet -> Manage Connections check under the Options tab that the 'Network Hotplugging' option is NOT selected.
I suppose you can still get eth0 up by typing 'ifup eth0' or 'ifup ifcfg-eth0' as the superuser from the terminal ?
I vaguely remember a problem like that in Mandrake 10.0. It seems to me a
work-around was to edit my /etc/sysconfig/network-scripts/ifcfg-eth0 file and
change the line saying MII_NOT_SUPPORTED=no to a "yes" instead. Then
it worked for me, when it stopped expecting MII to work for my card. Your
mileage may vary, of course. (As I recall, the kernel log showed that my card
did indeed have MII and the kernel knew it, so I decided the problem/bug was
higher on the food chain.)
if so:
become root in a terminal (su)
type:
"ifconfig eth0 down"
"dhclient eth0" and if it says command not found try "pump eth0"
-if they both say command not found do "apropos dhcp" and it will give you some info.
if you set your ip manually, just use the command:
"ifconfig eth0 192.168.0.1 up" and replace it with your ip obviously.
-if you connect directly to the net you should be fine but if you use a router or another computer as a gateway you'll have to tell that to the kernel:
"route add default gw 192.168.1.1" etc.
and also, /etc/resolv.conf holds your info about dns , where each line takes the form
"nameserver x.x.x.x"
it would be really gross to have to do that every time... but you can at least use it to make sure that your card works. if it still is being stupid you should check to make sure that the module is loaded. that info will be located inside /proc
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.