virtualbox.org

Installed vbox and Ubuntu Hardy Heron AMD64 guest could see host (Debian Lenny AMD64) without me doing anything. NAT was selected in network dialog thing. (Incidentally it pings OK, manual seems to say this never happens??)

Need for host to be able to see guest on network. So did what it seems to say in manual: changed NAT in network dialog thing to 'Host interface', I think it was.

Now if do: $ ssh 192.168.10.10 in guest nothing happens at all. Eventually have to do ctrl+c.

How to get host to see guest? Thanks any help.

Ping now works in NAT mode, this was introduced in 2.1.0.

As for your question with HIF and Guest in your network, this should work. However, you might have an improper config, or there is a firewall on the Guest. Does it actually run an SSH server?

Sasquatch wrote:Ping now works in NAT mode, this was introduced in 2.1.0.

As for your question with HIF and Guest in your network, this should work. However, you might have an improper config, or there is a firewall on the Guest. Does it actually run an SSH server?

No it was not running an sshd server only the host was doing this.

I do now have a functioning network after much buggering with bridges and taps (cannot even find out what a tap is, scream). Incidentally, with ssh, nautilus on the Ubuntu guest seems to give what ammount to nfs - where you may hang a remote file system on your own directory tree: file -> connect to server -> <select SSH>.

However, since you appear to be suggesting that all it lacked before was an sshd, I'll get rid of the bridge etc. and just try selecting 'Host Interface' and see if it works like that.

I know this is true of everything in Linux but why the hell cannot it be spelt out how to set up the bridge etc., say???? I read the tutorial here but it did not tell you the address of the host, that the guest needed an address, to install daemons, etc. ad nauseam. I repeat SCREAM!

Great thanks for your help.

I misread your first post. I though you wanted to SSH _to_ the Guest, not _from_ the Guest to the Host.

Default setup, meaning you select the physical interface that has full network connectivity, works as it should. At least on my side. There is no need for TAP interfaces (Virtual Interfaces) unless there is not always a connection on one of your physical adapters and you want a permanent connection to your Host.
If there is a DHCP server on the network, the Guest should get an IP automatically if it's configured to do so.

If you can't get it to work without all the bridges and TAPs, please post your full config of your network and what isn't working.

Got rid of bridges and taps and just made sure there was an ssh server, sshd, type thing on the guest. Selected 'Host Interface' rather than NAT on the VirtualBox screen thing. Gave the guest its own number and nickname 192.168.10.12 ubu. Then full network integration with the host's own network. So VirtualBox is really very idiot friendly in regard to networks. (Apropos of nothing the guest uses eth1, not eth0, as the virtual NIC - think it does anyway, the host has always insisted on doing this too. Surely it is usual to use eth0.)

My above remark about Nautilus file browser being equivalent to nfs was a bit over optimistic, there is stuff it won't do which nfs will. Problem solved with your help, sucessful thread, thanks very much.