virtualbox.org

Hello,

I read the docs and googling about my problem and i didn't find anything, so the moment has come to ask for help...

So i have a windows XP host and a debian guest. By setting a NAT network, i installed a standard version of debian 5.0 (kernel 2.6.26) with net installer. I didn't install guest addition because i think it is no necessary, i don't want a graphic environment or usb support... My project is to have a debian VM and access with ssh only...(don't break three legs to a duck (french expression litteraly translated))


After this i tried to set up a "real" network in my VM debian...

First with VirtualBox 2.2, i did a bridge network.



Then that's the problem :
i don't get an ip adress form the dhcp.
I tried the same configuration on a windows guest and it worked perfectly.

eth0,eth1 does not appear in ifconfig, but eth1 appear in ifconfig -a



if i try : ifup eth0

SIOCSIFADDR: No such device
eth0: ERROR while guetting interface flags: No such device



if i try : ifup eth1
Ignoring unknown interface eth1=eth1

Perhaps it's me or not but i really don't know how to do this (or get help)
I don't think the problem come from the configuration because the same configuration works perfectly on windows guest...
I tried also with virtualbox 2.1.4, and i've got exctly the same problem...

Here a last screen of lscpi, just in case of :


Thanks
Rénou

Try the other virtual adapters.

I have the same problem and spent my lot of time on the troubleshooting and just know it's bridge problem that Virtual box will not automatically install the bridge network card to the guest, this may make me crazy and almost want to uninstall VBOX but return to VMware, sigh....

and also, I feel so stupid for the networking behaviour, I am unable to change the connection type such as change from Bridge to NAT or change to host only during the GuestOS running...with this limitations, I sometimes unable to do lab testing on different networking mode..

still have no found the solutions for the Bridge mode, can't get IP from DHCP automatically at all.

seek anyone who can help on this...

Keep post please, thanks in advance.

yeahhhhhh, hmm sorry...

But it works now....

So, if you google (that's a verb isn't it) "SIOCSIFADDR virtualbox" you find this in the first results :
(of course, i read that yesterday but i really not thought that what was my problem)

http://ubuntuforums.org/showthread.php?t=221768

You have to change mac adresse in /etc/iftab... But i don't have this file on my VM...

So regoogling, and find this : http://ubuntuforums.org/showthread.php?t=698729

I modify this file : /etc/udev/rules.d/70-persistent-net.rules
and put my adresseMAC in eth0 (and change the MAC adress in eth1)... and reboot...
no more errors, dhcp give me an IP, and ping www.google.com responds !!!


so [SOLVED]
But i didn't what happened how my MAC adresse goes to eth1 instead of eth0 !!!

that doesn't work for me...anytime I changed the mac into eth0, it will auto add eth2, eth3, eth4, etc...faint....

I followed to change the 70 and 75 file, still with no luck.

deleted them and still no luck...

poor me and the bug.

VB2.2 + Bridge created a PAN0 and seems it get a 169 subnet ip...ai...

Heiguo, you're using your bluetooth connection for HIF? PAN0 is the Personal Area Network which is used by BT devices. You can't expect that a DHCP server is running on that connection.

Sasquatch wrote:Heiguo, you're using your bluetooth connection for HIF? PAN0 is the Personal Area Network which is used by BT devices. You can't expect that a DHCP server is running on that connection.

I didn't use any bluetooth connection, my environment is quite clear: Win2003x64 (non server role) installed VBox2.2, setup Ubuntu server 8.10 as VM and want to use Ubuntu to get IP from DHCP, and don't know what is PAN0 and how this comes out...

I had to setup Ubuntu 8.10 Desktop version again with default setup, and still same... PAN0....no such device at all....

any idea?

I have an idea, but that requires something you obviously lack, and that is to look beyond the obvious. You can select which NIC to use for Bridged mode. So unless you repaired the install, you can't select another NIC. Repair it, like it's noted here a dozen times, then select the NIC you need.

thanks but I tried this still failed either...

Sasquatch wrote:I have an idea, but that requires something you obviously lack, and that is to look beyond the obvious. You can select which NIC to use for Bridged mode. So unless you repaired the install, you can't select another NIC. Repair it, like it's noted here a dozen times, then select the NIC you need.