Changes between Initial Version and Version 1 of Ticket #13695
- Timestamp:
- Dec 16, 2014 10:13:00 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #13695
- Property Priority blocker → major
-
Ticket #13695 – Description
initial v1 1 1 Configuration: VirtualBox on Windows 7 using NAT, a bridged adapter and a host-only adapter. Guest OS is FreeBSD 10.0 2 3 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. 2 {{{ 3 VBoxManage modifyvm "FreeBSD-Router-10.0" --nataliasmode1 sameports 4 }}} 5 does not work (it appears to be ignored). The command succeeds, however there no effect on the NAT behavior. 4 6 5 7 I have tried a number of versions back to 3.2.16, and it does not work there either. … … 7 9 Have absolute verification that the ports ARE being changed by: 8 10 9 1)Starting the VM10 2)Establish a connection (in this case, using SSH)11 3)Look at the source port as reported by the VM (netstat -n)12 4)Look at the source port as shown at the far end13 5)The ports are different.14 6)Connect to the same machine without using NAT - the ports are unaltered.11 1. Starting the VM 12 2. Establish a connection (in this case, using SSH) 13 3. Look at the source port as reported by the VM (netstat -n) 14 4. Look at the source port as shown at the far end 15 5. The ports are different. 16 6. Connect to the same machine without using NAT - the ports are unaltered. 15 17 16 18 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!!

