vboxbnet disapear and/or change their ip => check with 3.0.4

[alior101]

after setting 3 vboxnet with ip 192.168.1.1/15/155 (no dhcpd). I check in the cli with ifconfig and see only vboxnet0 and 1 with correct ip. I reopened the vbox manager and reentered all vboxnet and this time ifconfig shows them all. after starting the vm and checking the ip's - they are all changed to the ip of the first vboxnet0.... I'm running ubuntu jaunty with latest vbox (3.0.2)

[hmw]

Hi,

I might have a similar problem on a Debian host system. A had created two (or more) host only networks with disjunct subnets (via File/Preferences/Network). Checking with ifconfig on the host doesn't reveal any problems. If I start a VM that has it's NIC bound to the second host only network, the IP adress of the corresponding virtual adapter on the host system changes to the IP adress of the virtual adapter of the first host only network. So both share the same IP configuration. This change is reflected in the Network dialog of the GUI. Shutting down the VM doesn't revert the configuration of the virtual interface back to it's desired state.

The same behaviour is observable if I manipulate the xml configuration file directly with a third party tool.

IIRC the problem wasn't introduced in 3.0.2. I can dimly remember similar behaviour in 2.2.x, but with worse effects to the Network dialog, like forgetting the second host only interface etc.

I really like to see this fixed. If you need further information or clarification feel free to ask.

Regards hmw

[Frank Mehnert]

There was a related bug which will be fixed in the next maintenance release. Note that when you add more host-only network adapters, the new adapters will have the same IPv4 address as the other adapters so it is required to immediately edit the settings of a new host-only adapter.

[hmw]

Hi,

sorry, for me the (mis)behaviour doesn't change with 3.0.4-50677_Debian_etch.

Regards hmw

[Frank Mehnert]

This was finally fixed in VBox 4.0.4.