I took the plunge and changed from NAT to "bridged adapter" and I was
able to ssh in - thank you for giving me the impetus.
There are consequences of that change, I'm not sure what they all are
... so I won't leave it like this, but in order to figure out how to get
my system up-to-date, it'll be useful having a properly functioning
terminal.
On 2020-06-14 18:02, antlists wrote:
On 14/06/2020 08:01, n952162 wrote:
I think the problem is, vbox's NAT interface acts as a router, but only
uni-directionally. That means, it will establish a "connection" for
VM-initiated sessions, but there's no mechanism for establishing a
session for external-initiated sessions.
Somebody, please correct me if that is wrong or incomplete.
I think that's true of any NAT interface.
Can't remember what it's called (bridge, maybe?), but that asks your
local LAN DHCP for an IP address, so you could ssh in from the local
network. It *should* be as simple as going into VirtualBox and
changing the setting.
Cheers,
Wol
