virtualbox.org

Hi,

Unable to do portforwarding with NAT can anyone help, here is a copy of the log: Kind regards
hotdog12

This error:

Failed to redirect TCP 127.0.0.1:2222 -> 0.0.0.0:22

looks very suspicious to me. Tell me you are not actually trying to redirect to 0.0.0.0:22, please.
Because if you do, then it means that you misunderstand the concept of port forwarding.
You may only set up port forwarding knowing the exact destination beforehand.
Think about it, how the system is supposed to guess which host you want to connect to when you reach your localhost at port 2222 ?
It just has no means of doing so. So forwarding to 0.0.0.0:22 is plain incorrect.

If you don't in your configuration try to redirect to 0.0.0.0:22, then it must be some bug.

Nope, this is purely virtual box setting up a box. I have not preset any port forwarding with those details.

Any other suggestiins?

I'd like to see the "recipe" of the VM, the ".vbox" file:

1. Right-click on the VM in the VirtualBox Manager. Select "Show in Explorer".
2. ZIP the selected ".vbox" file and attach it in your response.

Not a problem I'll sort that this evening.

Here we go as promised, any info that can help is greatly appreciated

Hmm... I can't see anything wrong with the rule itself. There is a difference in the recipe (.vbox) between your VM and a test VM that I made. Yours are:

• <NAT>
    <DNS use-proxy="true"/>
    <Forwarding name="ssh" proto="1" hostip="127.0.0.1" hostport="2222" guestport="22"/>
  </NAT>

while mine are:

• <NAT>
    <Forwarding name="guestssh" proto="1" hostip="127.0.0.1" hostport="2222" guestport="22"/>
  </NAT>

Funny thing is I don't know how to change this additional setting from the GUI. For the CLI I assume that you used "VBoxManage modifyvm <VM> --natdnsproxy1 on".

Here are the relevant parts from the logs. Yours:

• 00:00:01.535390 NAT: Guest address guess set to 10.0.2.15 by initialization
  00:00:01.538079 NAT: DNS#0: 188.120.239.115
  00:00:01.538087 NAT: DNS#1: 8.8.8.8
  00:00:01.561154 NAT: Failed to redirect TCP 127.0.0.1:2222 -> 0.0.0.0:22 (Unknown error)

and mine

• 00:00:01.733409 NAT: Guest address guess set to 10.0.2.15 by initialization
  00:00:01.752920 NAT: resolv.conf: nameserver 10.0.0.1
  00:00:01.752973 NAT: Adding domain name Home
  00:00:01.752978 NAT: DNS#0: 10.0.0.1
  00:00:01.753061 NAT: Set redirect TCP 127.0.0.1:2222 -> 0.0.0.0:22
  

You see that both in the configuration and in the logs, the differences are in the DNS. You obviously changed something in the DNS configuration for the VM. I'm not sure if and how it affects it. It shouldn't, but that as far as my limited experience can go.

Finally, I see a couple of unusual settings in the .vbox:

• <ExtraData>
    <ExtraDataItem name="VBoxInternal2/SharedFoldersEnableSymlinksCreate/var_www" value="1"/>
    <ExtraDataItem name="VBoxInternal2/SharedFoldersEnableSymlinksCreate/var_www_public" value="1"/>
    <ExtraDataItem name="supported" value="false"/>
  </ExtraData>

Did you create the VM in VirtualBox? Or did you use a 3rd party tool (Vagrant, Docker, etc)?

Under extra I have used vagrant, hence the sync folder. However this issue is preventing the syncing happening.

Any tips I can do to resolve this?

Also thanks for the help, this is helping me narrow this down a lot further.

Hotdog12 wrote:Any tips I can do to resolve this?

Yes, build a VM from scratch from within VirtualBox alone. Vagrant is a program that relies on VirtualBox but modifies its configuration files in unknown ways to us. It is not supported on these VirtualBox user forums, they have their own vagrant support channels. If you are having this problem with a standalone version of VirtualBox, then we can continue this discussion.

Okay so to understand vagrant sets the xml up (.vbox file) and virtual box just simply runs that configuration?

I have no clue. I have never used Vagrant.

Okay no problem. The info you have isolated should allow me to investigate this further. I'll add any new information I find out just so it's documented