Using Pallet actions against NAT-networked vmfest node

[Jon]

We're using pallet-vmfest to provision VirtualBox-hosted nodes.  Because IP addresses are very limited on our LAN, we're currently having to use NAT as the networking mode.  No problem spinning up such machines, and no problem ssh-ing manually to the port which pallet automatically causes VirtualBox to auto-forward to the VM.  We can also use pallet-actions/exec-script* to execute arbitrary bash, which is handy.

However, when we try to use pallet.actions/rsync-directory against such a node - and probably other actions too - the operation fails because Pallet tries to reach the VM's sshd using an inaccessible IP address (the IP address the remote node sees itself having) and port 22 (which is what it exposes internally, but isn't what VirtualBox has been pallet-configured to expose externally and forward on).

I'm about to dig around to see if pallet.actions/rsync-directory and other actions expose any config I can set directly ("use _this_ address and this port!") but that feels wrong and may not even be possible, and I'd have hoped Pallet could use data derived directly from the node it provisions.  Is that right, and can anyone provide any pointers?

Jon