Bridged Networking with 2 interface on openSuSE11 (VB 2.2.2)

[empi]

Hi fellows,

I just installed VirtualBox 2.2.2 on my openSuSE 11.1 (amd64) system.
This Host has 2 Network interfaces:
eth0: 10.1.253.240 / 255.255.255.224
eth1: 192.168.8.1 / 255.255.255.0 (unplugged)

I imported an Ubuntu Server 8.04 as the Guest OS and configured it to use bridged networking

Code: Select all

 VBoxManage modifyvm "ubuntu-server" --nic1 bridged --bridgeadapter1 eth1

within the ubuntu Server i configured my networking device like this (don't know why eth2 is coming up instead of eth0)
but I can't communicate with the eth1 device of my host system. Neither PING nor SSH are working.

Code: Select all

auto eth2
iface eth2 inet static
  address 192.168.8.2
  netmask 255.255.255.0

However if I'm configuring my device to use the same network like the eth0 of my host - it works to connect to 10.1.253.240 from inside the VM.

Code: Select all

auto eth2
iface eth2 inet static
  address 10.1.253.239
  netmask 255.255.255.224

I also tried to modify my VM to use eth0 instead of eth1 as the bridge without success.

Do you have any ideas what I can do to solve this missbehaviour or at least any steps to verify where it comes from?
In the end, if this has something to do with the 1st and the 2nd device of my host system I'll just switch the configuration.

Any help appreciated
Please save your breath for anything like "Have you read the manual?" I've almost memorized it
Best Regards
empi

[vbox4me2]

eth1 is unplugged and you're talking about eth2... you may need to rethink what your doing on what interface.

[empi]

due to my understanding of network interfaces it doesn't need to be physically connected to be usable.
Otherwise you couldn't connect to yourself on a standalone host without any physical connection.
So I was assuming that the VM and the Host could communicat over their virtual connection on the same interface.

I went to my server to see if plugging in brings any improvement regarding to the "virtual" communication.
I succeeded, now I can communicate between the Host (eth1) and my VM (eth2) on 192.168.8.0/24 just by plugging in a placebo cable - weird

sorry for bothering

Best Regards

[Sasquatch]

due to my understanding of network interfaces it doesn't need to be physically connected to be usable.
Otherwise you couldn't connect to yourself on a standalone host without any physical connection.
So I was assuming that the VM and the Host could communicat over their virtual connection on the same interface.

I went to my server to see if plugging in brings any improvement regarding to the "virtual" communication.
I succeeded, now I can communicate between the Host (eth1) and my VM (eth2) on 192.168.8.0/24 just by plugging in a placebo cable - weird

sorry for bothering

Best Regards

Oh yes it needs to be connected. If it's not, it's brought down and the config is released. If you know a bit about Cisco, it's the same as having the interface in shutdown mode. You can't communicate with an interface if no data can go out or in.