I moved my post: https://forum.pfsense.org/index.php?topic=85168.0

I see, thank you for the explanation. I'll take a look at Esxi.

But the "ifconfig mtu" commands are temporary aren't they? Wouldn't they be reset to whatever setting I have in the GUI? (which also hasn't worked for me after a reboot). Any idea why I might be seeing different results on the native hardware (which was also without a reboot) M

Don't mention it, and don't take anything said above personally.  You gotta roll with the punches in the tech trenches.

Yes, that was the issue! Thank you! Weirdly enough, when checking for Updates in VB it said that it was up to date. I had to manually download and replace the version. After setting up the VM again, it finally works.

I think this might be related to our issue https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059 Another thing that we noticed, if we enable TSO on the pfSense vtnet interfaces, all traffic to the VMs on the same host as the master pfSense firewall gets stuck. Traffic going via the master firewall but to a VM on a different host is fine.

@johnpoz: No B is Bytes, b is bits - that is how it is everywhere!! http://en.wikipedia.org/wiki/Bit the lower-case letter b is widely used as well and was recommended by the IEEE 1541 Standard (2002). In contrast, the upper case letter B is the standard and customary symbol for byte. doing /sec vs ps is 2 different ways to say the exact same thing per sec. So your doing it wrong ;)  And I can not believe you have ran into confusing before ;) My bad. I'll be more clear in the future :D -Jamie M.

It will load but cant take something like 30 mins.  :-\

You can do port forwarding if you are ok with using ports like your example :5700 and :5600 https://doc.pfsense.org/index.php/How_can_I_forward_ports_with_pfSense You would use a reverse proxy if you want to allow access via dns name that all points to your one public IP.  so for example www.yourdomain.tld points to 192.168.1.158, while ftp.yourdomain.tld points to .159  If your ok with just using ports on the url like you gave in your example than a simple port forward works.

@Asgaroth: I would be interested in a howto on SmartOS and pfsense:) The only issue I have with smartOS at the moment, and also, the only reason it is not running here at home, is because the kvm implementation on SmartOS does not have pci passthrough support yet (it's been a while since I checked if they support it now, but the last time I checked there was no pci-passthrough support (vt-d) in smartOS) I'm a fan of ZFS and only just discovered Joyent SDC and SmartOS so I could see myself ending up there in the near future and will then need a pfSense instance so I'd love to see more support.

I run tools on pfsense 2.1.5 i386 and never have any issues, are you running amd64, then there is a thread about comment out part of the vmware tools script that creates the not configured file. I have updated the docs for vmware tools that touches on this subject. https://doc.pfsense.org/index.php/VMware_Tools If you are having problems with tools not starting on reboot, you can edit /usr/local/etc/rc.d/vmware-tools.sh Have not seen this on 32bit pfsense, but have seen reports on 64 after say 2nd reboot Comment out the whole section if [ "$exitcode" -gt 0 ]; then     # Set the 'not configured' flag     touch "$vmware_etc_dir"'/not_configured'     chmod 644 "$vmware_etc_dir"'/not_configured'     db_add_file "$vmware_db" "$vmware_etc_dir"'/not_configured'     "$vmware_etc_dir"'/not_configured'     exit 1     fi

And is there a not_configured file?  If so you didn't comment out the .sh correctly.

Build  1623387?  That is Update 1, way back in March..  Yeah I would update lots of changes and fixes and drivers updated, etc.

Use the 2.2 beta for better hyper-v support or run ifconfig hn0 down ifconfig hn0 up (dhclient hn0 only if hn0 get his ip by a DHCP server) ifconfig hn1 down ifconfig hn1 up after every start of your vm