интернет на debian в virtualbox

# program, run by the persistent-net-generator.rules rules file.

# This file was automatically generated by the /lib/udev/write_net_rules

cat /etc/udev/rules.d/70-persistent-net.rules

Here’s the reason why Debian removed eth0

RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)

TX packets:8 errors:0 dropped:0 overruns:0 carrier:0

RX packets:8 errors:0 dropped:0 overruns:0 frame:0

UP LOOPBACK RUNNING MTU:16436 Metric:1

inet6 addr: ::1/128 Scope:Host

inet addr:127.0.0.1 Mask:255.0.0.0

lo Link encap:Local Loopback

If you run ifconfig, you’ll see that there’s just a loopback interface but not network connectivity:

It’s just a matter of seconds and you have your new system up and running! Pretty cool! Is it? You’ll realize that you won’t have any network interfaces available. This is oft course not a new issue, lots of people have reported this and it’s easy to fix but I always forget where that file is located we have to modify. Usually when I write about something, it’s easier for me to remember it. This is a pretty selfish article!

After you click on that dialog, you’ll be presented with another dialog where you can tell VirtualBox to assign a new MAC address. As I often run several virtual machines at the same time, I always tick this checkbox.

Unfortunately there’s one little change you have to make…

I often work with virtual Debian instances to test new stuff. In order to reduce the likelihood that another test I’ve run before interferes with the new test, I clone them. I’ve installed a base system which runs using . Whenever I want to test something new I just clone it with this neat little function:

Published on 20 June 2012 under

No Network in Debian after Cloning with VirtualBox

Coding and more – Concrete5, Flex, JavaScript

No Network in Debian after Cloning with VirtualBox « CodeBlog.ch