VirtualBox

Opened 13 years ago

Closed 13 years ago

Last modified 9 years ago

#8094 closed defect (fixed)

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

Reported by: appyface Owned by:
Component: other Version: VirtualBox 4.0.0
Keywords: Cc:
Guest type: Windows Host type: Windows

Description (last modified by Valery Ushakov)

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

Change History (10)

comment:1 by vasily Levchenko, 13 years ago

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

thanks for reporting, issue is fixed in svn.

comment:2 by vasily Levchenko, 13 years ago

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

comment:3 by vasily Levchenko, 13 years ago

Thanks for reporting, issue is fixed in SVN.

comment:4 by appyface, 13 years ago

Awesome, thank you so much :-)

comment:5 by Frank Mehnert, 13 years ago

Resolution: fixed
Status: newclosed

comment:6 by chad, 9 years ago

This bug seems to affect vbox 5.0 possible regression

comment:7 by Valery Ushakov, 9 years ago

Description: modified (diff)

in reply to:  6 comment:8 by Valery Ushakov, 9 years ago

Replying to chad:

This bug seems to affect vbox 5.0 possible regression

Any details? Works for me.

comment:9 by sinzim, 9 years ago

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.

in reply to:  9 comment:10 by Valery Ushakov, 9 years ago

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.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use