VB 3.0.1, mulit-homed host, problems with bridged adapter

Discussions related to using VirtualBox on Linux hosts.
Post Reply
mrpetkus
Posts: 6
Joined: 16. Jul 2009, 17:32
Primary OS: Debian Lenny
VBox Version: OSE Debian
Guest OSses: Debian, Windows

VB 3.0.1, mulit-homed host, problems with bridged adapter

Post by mrpetkus »

Folks,
Background:
* Debian Lenny amd64 host system with multiple NICs
* Multiple Debian Linux guests, 32 and 64-bit

Goal:
* Persistent binding of NIC to a specific VB guest using a bridged adapter.
* Guests will use a static IP address accessible from "outsite".

Problem:
If I do either of the following:
1. New way:
- Select "Bridged Adapter" and bind to eth1
- Bring up eth1 interface: ifconfig eth1 0.0.0.0 up
- Boot guest
2. Old way:
- Create tap interface, bind tap0 to eth1
- Select "Bridged Adapter" and bind to tap0
- Bring up tap0 interface: ifconfig tap0 0.0.0.0 up
- Boot guest

The VB guest boots fine and is accessible but if I REBOOT the guest, I have no connectivity.
Why?
Why does it appear to be a one-shot deal?
What am I doing wrong?

If I bring eth1 or the tapped interface down and up, restart the host network stack, still no-go.

Thanks in advance
Post Reply