Today on my Munich-Florence train, I've waisted some time just trying some ways for "sshing" my puppet VirtualBox guest.
Usually DHCPclient does everything and, once the ip address is got by the guest, I can easily "ssh" into it.
This time, I had not a wifi connection and I've encoutered some annoying bounces on my ssh attempts. It looked like the guest was unreachable. I've instinctively tried every "nat", "bridged", "host-only" options.. and in the end .. it touched me to read the documentation :) (by the way, a very good paper)
..and it was so i've discovered this official best practice to port-forward services on a VirtualBox guest
In this example (exactly extracted from the doc), we are going to portforwarding the SSH service, from our HOST 8888 port, to the GUEST (vm name: "Puppet Test Machine") on 22 port:
"sshService" is just a label.
In this way, our HOST will keep the forward on each interfaces. Anyway, it's possible to bind a specific interface though.
Now that we have our forward ready, we can connect the loopback on the given port
This rule will be permanet unless you explicitly remove it.
See the rule properties:
Then delete the rule:
