Fusion 3: incomingtcp cleared after every network startup

[brow2938]

I've tried all the normal ways to get a TCP port published from my NAT network (vmnet8).

Stop networking services:

sudo /Library/Application\ Support/VMware\ Fusion/boot.sh --stop

Edit my nat.conf file for vmnet8. I'm adding the following:

8080 = 172.16.45.128:8080

Restart networking services:

sudo /Library/Application\ Support/VMware\ Fusion/boot.sh --start

Once started, I check my nat.conf file and the incomingtcp section is blank again. That section gets cleared after each restart of the network services (including reboot).

Any recommendations?

[brow2938]

Looking closer at the "start" command, part of the output says...

...

/Library/Application Support/VMware Fusion ~

Stopped all configured services on all networks

Backed up existing network settings to backup file "/tmp/vmware.o0ghDv"

Restored network settings

~

...

I'm not sure why the "start" first backs everything up, then restores it immediately, but I assume that's where the problem is. Changes can't get merged into this process.

I've looked in the boot.sh file for this "backup" procedure (to comment it out), but don't find it. It must be part of one of the binaries... if this is the problem.

[brow2938]

OK, I found the problem in boot.sh. It appears a check the script was doing was resulting in "TRUE" every time, so networking was being reconfigured every time (and changes were being overwritten). The problem section was:

1. Configure networking if the 'networking' file is missing or*

1. is older than 'vmnet-cli', i.e. installed files.*

net_time=`stat -f %c "$LIBDIR/networking" 2>/dev/null` || net_time=0

cli_time=`stat -f %c "$LIBDIR/vmnet-cli"` || cli_time=0

if ; then

pushd "$LIBDIR"

"$LIBDIR/vmnet-cli" --configure

popd

fi

To fix this I put "echo" in from of the "$LIBDIR/vmnet-cli" --configure line.

[sprotsman]

Thank you. Trying to figure this out after my Fusion 3 upgrade was beginning to be a real time suck. Thanks for posting this quick fix. Now I can get back to work.

[sprotsman]

Version 3.0.2 has been released and this problem remains. Come on VMware, get this fix into the product so we don't have to keep rebuilding our NAT rules (nat.conf) and hacking the boot.sh script just to have this functionality.