cah Bojonegoro

I have a virtual machine in here used to automate a backup process & reporting purpose. It is an Ubuntu JeOS inside a windows machine using Sun Virtual Box. I create this since they didn’t provide me login to any Unix Machine, instead of they give me a windows PC. Worse, the account didn’t had any administrative privileges.

I managed to request them to installed Sun VirtualBox inside this PC. But the sys admin said to me, do you have the license for this program ??

Forget it, it had been installed anyway and It is working for about 2 months.

But today the problem is after i play around with the Virtual Box networking, i ended up with making the Virtual Machine isolated from the outside world. Yes, the only interface detected is only loopback. Where in the earth is eth0 gone.

Several time to change the setting on Virtual box networking, but still didn’t get the etho appear inside the VM. Suspected that the Sun xVM is having problem with its networking, i create another VM using TinyME live CD and i found out that NAT is working properly. So, it is got to be something happened with the Ubuntu JeOS.

From dmesg, i got this error.

heric@jeos:~$ dmesg | grep eth0
[    9.843856] eth0: registered as PCnet/FAST III 79C973
[   15.560583] udev: renamed network interface eth0 to eth5

so, why udev renaming my eth0 to eth5 ?

I check in udev rules & found out that there are several ethernet interface in the in /etc/udev/rules.d/70-persistent-net.rules.

heric@jeos:~$ more /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:e7:d3:34", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:1d:7d:f2", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:f1:14:ae", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:57:65:84", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:af:39:5c", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"

# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:86:50:a8", ATTR{type}=="1", KERNEL=="eth*", NAME="eth5"

I should have only one eth interface in this file. But, as a result playing around with VBox networking, in my Virtual Machine i had 5 udev rules for 5 different ethernet MAC Address, that’s why udev rename my eth0 to eth5, and VirtualBox doesn’t recognized this eth5.

Well, the solution is simple, i remove all udev rules in this file & reboot the machine.
When it is come up, the outside world is visible again

---

« « Tip Bekerja dengan Gambar di Blog

The power of apt-get » »

---