This article is step-by-step tutorial how to fix a problem which occured after I restored my virtual machines from backup to my ESXI server.
when I used lspci, result was
So network adapter is correctly available in my virtual machine. As next step I need to found out which alias is used for this adapter. I didn’t find any easily way than try et0,eth1,….
ifconfig eth0 eth0: error fetching interface information: Device not found ifconfig eth1 eth1: error fetching interface information: Device not found ifconfig eth2 eth2: Link encap: Ethernet HWaddr.....
So, I found my network adapter. Now as last step it’s necessary to update network interfaces to this adapter
sudo nano /etc/network/interfaces #and change all eth0 to eth1 values
As last step restart your machine and everything should work correctly.
You’re a lifesaver! Thanks so much, this fixed an issue I just couldn’t figure out.
found 5 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!
Process with PID 5254 (dhclient) is running on interface eth1
Interface Chipset Driver
eth1 Unknown wl – [phy0]mon0: ERROR while getting interface flags: No such device
(monitor mode enabled on mon0)
this is what i get when i try to use airmon-ng start eth1
I’m getting same problem, been seargin the interweb all day with no luck….
It is really very helping to me and my friends.. We are very thankful to you..
Thank you very much…..
a really great works! I was quite desperate!!!
Thank you. It works like a charm
Thank you very very very much! my friend! : D: D
I had this problem and did not know how to solve it ..
Be well! :))
Ubuntu keeps track of the association between MAC addresses and interface names in /etc/udev/rules.d/70-persistent-net.rules
When you restore the VM on a different server, the network connection has a different MAC. eth0 is still associated with the old MAC (because of this file), so the new MAC address is allocated the next available ethX interface. (Since you ended up with eth2, you probably have existing rules for eth0 and eth1)
You can edit that file and remove the old rules but unless you have some complicated networking requirements, just remove the file and reboot and you will find your network connection on eth0 as you originally expected.
sudo mv /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/70-persistent-net.rules.old
Naturally, if you have followed the steps in the original post and changed /etc/network/interfaces then you need to revert that back to eth0 🙂
(“ifconfig -a” might have been useful for you!)
Very helpful, thank you very much.
Helped me get the VirtualBox bridged adapter to work with Debian 6.
Thanks for this post. I used this on Debian.
Thank You very much. Solved my problem with Freepbx on CENTOS. We saved lot of hours of web searching.
This information save my life.
Thanks a million.
This was just the thing i needed.
Me ajudou muito