Opened 10 years ago
Closed 8 years ago
#13695 closed defect (duplicate)
nataliasmode1 --sameports does not function
Reported by: | SteveC | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.3.20 |
Keywords: | Cc: | ||
Guest type: | BSD | Host type: | Windows |
Description (last modified by )
Configuration: VirtualBox on Windows 7 using NAT, a bridged adapter and a host-only adapter. Guest OS is FreeBSD 10.0
VBoxManage modifyvm "FreeBSD-Router-10.0" --nataliasmode1 sameports
does not work (it appears to be ignored). The command succeeds, however there no effect on the NAT behavior.
I have tried a number of versions back to 3.2.16, and it does not work there either.
Have absolute verification that the ports ARE being changed by:
- Starting the VM
- Establish a connection (in this case, using SSH)
- Look at the source port as reported by the VM (netstat -n)
- Look at the source port as shown at the far end
- The ports are different.
- Connect to the same machine without using NAT - the ports are unaltered.
This is a complete show stopper because we depend on NFS mounts in a development environment. The issue is actually affecting a lot of people. No, unfortunately, we cannot modify the NFS server. Already have dents in my forehead trying to get that through!!
I will test anything you would like. Can provide information, VMs, etc. if needed. THANKS !!!! Regards, Steve
Attachments (1)
Change History (4)
by , 10 years ago
Attachment: | FreeBSD-Router-10.0-2014-12-15-16-35-36 added |
---|
comment:1 by , 10 years ago
Description: | modified (diff) |
---|---|
priority: | blocker → major |
comment:2 by , 8 years ago
Seeing same issue here. Ports are randomly changed even when set to use sameports. This affects other protocols as well that relay on a specific source port number.
Logfile