VBox 4.0 Can't use same port for TCP & UDP forwarding -->fixed in SVN

[appyface]

I posted my issue in the forum, Sasquatch confirmed and suggested I open a bug ticket here. Please see this thread:

​http://forums.virtualbox.org/viewtopic.php?f=1&t=38093&start=0

I can't get 4.0 to use same port for both TCP and UDP port forwarding?

In 3.x versions this has been working well using VBoxManage (early versions used "setextradata", later versions using "modifyvm" as shown here):

VBoxManage.exe modifyvm "my_vm" --natpf1 "tcp_pf",tcp,,32512,,32512
VBoxManage.exe modifyvm "my_vm" --natpf1 "udp_pf",udp,,32512,,32512

Now with 4.0 I can only set both rules if ports are not the same. Sasquatch confirmed in the GUI that the second rule is discarded. VBoxManage gives error message on the second rule, stating it already exists.

Kind regards,

--appyface

[vasily Levchenko]

thanks for reporting, issue is fixed in svn.

[vasily Levchenko]

Thanks for reporting, issue is fixed in SVN.

[appyface]

Awesome, thank you so much :-)

[chad]

This bug seems to affect vbox 5.0 possible regression

[Valery Ushakov]

Replying to chad:

This bug seems to affect vbox 5.0 possible regression

Any details? Works for me.

[sinzim]

Same problem in 5.0, try adding two rules in the GUI which use the same port but different protocols. It fails in my case.

[Valery Ushakov]

Replying to sinzim:

Same problem in 5.0, try adding two rules in the GUI which use the same port but different protocols. It fails in my case.

Thanks for being specific in your description. The problem indeed exists, but it's GUI problem. When the original bug was fixed, the GUI checks were not relaxed, apparently. You can use VBoxManage as the workaround.