Since VBox 2.1.0 you can attach a VBox hostif to a host interface which is either a phyiscal interface (like eth0 or wlan0) or a TAP interface (which you have to setup yourself).
Regarding your problem: I really don't know why ssh does not work but did you already check if there is no firewall which could block the transmission to specific ports? Try to switch of the firewall for both the guest and the host. Kind regards, Frank On Saturday 14 March 2009, JD wrote: > That's interesting. > Is that in the user manual? > I had tried it in the past (older versions of Vbox), > but always ended up having to set up the bridge, which > is not a straightforward procedure. > > JD > > Johannes Kastl wrote: > > On 3/12/09 11:40 PM Clint Dilks wrote: > >> I recently upgraded from VirtualBox-2.1.2_41885_rhel5-1.x86_64.rpm to > >> VirtualBox-2.1.4_42893_rhel5-1.x86_64.rpm on a CentOS 5.2 Host (64 > >> Bit). This trashed the bridged networking setup that I had configured > >> in 2.1.2 where I had vbox0 and vbox1 talking to br0. From reading the > >> new documentation it seems that I am now just supposed to select host > >> interface and then br0 which I have done. Generally this seems to be > > > > Im not sure, but I think all the "bridge"-hacking should no longer be > > necessary, you could use hostinterface with your "real" device (eth0, > > wlan0, ...). > > > > Regards, > > OJ > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > vbox-users mailing list > > [email protected] > > http://vbox.innotek.de/mailman/listinfo/vbox-users -- Dr.-Ing. Frank Mehnert Sun Microsystems http://www.sun.com/
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
