I've sent a message to Parallels support to check this issue, no useful answer for now. Waiting for that to happen, I try and avoid what "seems to be a bug" :
Code:
$ prlsrvctl net list
TCP rules:
my-service-1 source port=8030 destination IP/VM id={[my GUID]} destination port=8888
my-service-2 source port=5030 destination IP/VM id={[my GUID]} destination port=5020
my-service-3 source port=3330 destination IP/VM id={[my GUID]} destination port=3306
I see all my port forwardings, except the one for ssh.
So, I try and add it manually:
Code:
prlsrvctl net set Shared --nat-tcp-add ssh,2230,[my GUID],22
It seems ok :
Code:
$ prlsrvctl net list
TCP rules:
my-service-1 source port=8030 destination IP/VM id={[my GUID]} destination port=8888
my-service-2 source port=5030 destination IP/VM id={[my GUID]} destination port=5020
my-service-3 source port=3330 destination IP/VM id={[my GUID]} destination port=3306
ssh source port=2230 destination IP/VM id={[my GUID]} destination port=22
and then, using as usual :
Code:
$ ssh -p 2230 vagrant@localhost
I'm able to connect to the VM. So at least I have a way to move forward, but I'm still interested in understanding what's going wrong in the automatic process. Again, event with vagrant --debug, there is no mention or error messages concerning the ssh port forwarding instruction.