Allows you to search a variety of questions and answers
Sometimes after you reboot your Debian or Ubuntu machine, networking does not come up and it only shows 'lo' when running the ifconfig command. One possible explanation could be due to MAC addresses in the udev file as explained here: http://ubuntuforums.org/showthread.php?t=255018.
To work on this, you will need either access via IPMI or directly on the console.
After logging in as root, open up your /etc/udev/rules.d/70-persistent-net.rules file and delete the lines like below, noting the module name on the "# PCI device" line:
1. PCI device xxxxxxxxxxx (module)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="xxxxxxx", NAME="eth0"
This removes the MAC to eth device mapping info. Now we need to restart udev to allow the change to take effect:
/etc/init.d/udev restart
Next step is to "bounce" the kernel module for the ethernet device. Use the module name from the 70-persistent-net.rules file noted above:
modprobe -r module
modprobe module
"ifconfig" should now show the eth0 interface as up and running.
If, after you restart networking (/etc/init.d/networking restart) and running ifconfig -a still shows your eth devices as having a wrong number, you can go to udev file, manually change the ethx to eth0 and go through the udev and modprobe steps again. That should fix the problem.
I love AYK. been with them for over 5 years and the best ever
After getting a dedicated server from AYK for almost 2 years, I couldn't be more happy. The prices are very reasonable, I haven't experienced a moment of downtime, the support is excellent and truly 24/7. You have a critical issue at 2am? You will have it sorted out in less than 15 minutes. If you are looking for honest, reliable and affordable hosting provider, look no further!
Simply the best. have been using them from last 2 years. Remember Dedicated servers are hardware so few times problem do arrive. but always fixed in time. Really really Positive attitude from President.