Host Interface error after 2.0.6 -> 2.1.2 Fedora 8 Host/G
Posted: 23. Jan 2009, 01:41
Host Interface error after upgrading 2.0.6 -> 2.1.2 Fedora 8 Host/Guest
(I hit the character limit on the subject line, sorry.)
Alright, so I've prowled around the forums to try and track down any hints for what to do with VirtualBox's new net driver when it doesn't work. I have been using TAP interfaces to host samba shares for our school network on a virtualized (and therefore easily backed-up) server since v1.6.
The new drivers look really promising, and I'm using assigned IP addresses for both the host and the guest machine (they have assigned network names for students to connect to) so it should have worked smoothly once I loaded up the VM.
If it's as it worked previously, the guest machine's network settings should match those of the host, aside from it's assigned IP. The host interface driver should behave transparently, correct?
I've gone under Settings -> Network and selected Attach To: Host Interfaces, and specified eth1, the internet/WAN connection which I can ping the host machine on from anywhere on campus. When I boot up the guest machine with these settings, I can ping it from the host but am unable to see it from any other machine.
I get the same exact symptoms when I attach it to br0, the bridge that I was formerly using. I can use the samba shares, SSH to it, ping it, etc. from the host machine, but am unable to reach it at all from another computer on the network. I can do all of the above to the host machine, so it's not a general connectivity issue.
With the new driver, should the bridge have a specified IP address? (And if so, should that IP address match that which the guest machine will be using?)
I'll copy in the text from ifconfig for both host and guest here in a moment...
(I hit the character limit on the subject line, sorry.)
Alright, so I've prowled around the forums to try and track down any hints for what to do with VirtualBox's new net driver when it doesn't work. I have been using TAP interfaces to host samba shares for our school network on a virtualized (and therefore easily backed-up) server since v1.6.
The new drivers look really promising, and I'm using assigned IP addresses for both the host and the guest machine (they have assigned network names for students to connect to) so it should have worked smoothly once I loaded up the VM.
If it's as it worked previously, the guest machine's network settings should match those of the host, aside from it's assigned IP. The host interface driver should behave transparently, correct?
I've gone under Settings -> Network and selected Attach To: Host Interfaces, and specified eth1, the internet/WAN connection which I can ping the host machine on from anywhere on campus. When I boot up the guest machine with these settings, I can ping it from the host but am unable to see it from any other machine.
I get the same exact symptoms when I attach it to br0, the bridge that I was formerly using. I can use the samba shares, SSH to it, ping it, etc. from the host machine, but am unable to reach it at all from another computer on the network. I can do all of the above to the host machine, so it's not a general connectivity issue.
With the new driver, should the bridge have a specified IP address? (And if so, should that IP address match that which the guest machine will be using?)
I'll copy in the text from ifconfig for both host and guest here in a moment...