There should be no difference in hardware support, regardless of license level.

Thanks Marv21, that works

Your not the OP… Are you... Your saying your running the same hardware as him without any issues?  I doubt that to be honest since the board he mentions supports at max 64GB of ram..  And your stating you have over 100.. It's quite possible his box just can not push gig while yours can..  Ram not really the limiting factor here anyway.

I've been running pfSense on ESXi for many years and I've never seen anything like that.  Perhaps the ESXi host is rebooting and you have it configured to do a guest shutdown on your VMs?

That's somewhat similar to what I'm seeing and I'm using Xeon cores. When I'm going full gig from my LAN to WAN I sit around 10-15% CPU usage. You using an i3 would be a bit higher. Just part of virtualizing routers/firewalls. You figure they have to handle every single packet that passes through its interfaces.

Hello, The machine has one nic up and the first IP is assigned to that nic. I am not sure where the second IP is assigned but the following is the detailed network info for the vmnic1 adapter: [image: network.png]

Makes sense. I'm an amateur to most this, so my thought process was "if my VM (ubuntu) is compromised and someone directs its default gateway from 172.16.100.1 (physical router) to 172.16.100.2 (my pfsense), they now have some way to access my pfsense management interface." I was hoping to have my physical router do the vlan packet inspection and drop the packets that aren't generated from a certain vlan for no other reason than the router is built to be a very low resource/efficient router. I thought my vsphere config would cause all traffic to route to the physical router due to a separation of vlan, but that doesn't seem to be the case.

Good info, thanks. Gives me some direction. Still a lot to learn. I appreciate the help.

Notice my username "coconuts", I am living on a small outcropping of coral which is an island in the Pacific Ocean. Notice my username "KOM", which means 'frozen wasteland' in some language.  I am living on a small outcropping of ice which is currently freezing my ass. I hate you already.  ;D

This looks like its a FreeBSD issue. This bug has come and gone in a couple of version it seems. 9, 10 and 11 … I don't know what to make of the answers I get. Google keywords: FreeBSD 11.1 hyper-v write(6) CDB retrying command

That makes sense. Thanks for clearing that up.

After playing around with pfsense i have a few more questions, i have a ps4 and a PC connected via powerline, i would like to isolate these devices to "another" network for security reasons but i will need these devices to have internet access. How i can do that? can i create another bridge nic and asign it to pfsense as another lan port? Can you guide me with a few security tips in order to setup pfsense? If i need to create other VMs and connect them to my main network where i will bridge them?

@kiko83: question 1) please i need help to configure the network! on vmware workstation > virtual machine settings > i have added 2 network adapters, first one is  Bridget, but is not checked "replace physical network connection state", and another one network adapter is Host only. Question 2) which options are best for me to make this to work properly? do is needed to change the first adapter to another one?  or the option "replace physical network connection state" to be checked ? question 3) which is the procedure to make this thing to work? I would use a virtual bridged adapter on the NIC from "the network which is coming by lan" as WAN for pfSense, on the additional NIC (WI-FI?) on the host system I would disable all services except of the vmWare-Networking, add a bridged virtual adapter on it and use it as LAN for pfSense "do is needed to change the first adapter to another one?" - no, the "Host only adapter" should not be used for your configuration - it is in the "localhost" network, which can normally not communicate with physical devices, "replace physical network connection state" seems to be good for pfSense - it will see, if the physical cable is connected, the question is too general, try to look at the documentation of installing pfSense on a virtual host, e.g. https://doc.pfsense.org/index.php/Virtualizing_pfSense_on_Proxmox, to general pfSense installation documentation https://doc.pfsense.org/index.php/Installing_pfSense , to "getting started" guides, read this forum, etc.

I was having the same issue. Here's what fixed it for me: 1. Disabling the dest/source checks from the Instances panel only disables the check for the primary network adapter 2. Go to Network & Security > Network Interfaces 3. Right-click on the LAN adapter (172.16.0.1/24) and choose Change Source/Dest. Check -> Disable

@Derelict: Use the ID of the inside pfSense interface. BINGO! That was it. I had to manually copy the Network Interface ID for the LAN adapter on the pfsense instance and paste it into the target for my new default route for the private subnet (writing it out for others to easily follow what I needed to do to solve this). Thanks!

You can host anything you want on your VM setup.. Sure if you want to run Acitive Directory or LDAP.. have at it..

Well, I used the pfsense iso to get into single user mode, managed to fix errors with fsck to the point that I could copy config.xml and a few scripts I created to another volume and re-installed.

Read up one post. There is no identifiable problem with the firewall software. I would suggest starting another thread detailing exactly what you are seeing instead.

@yarick123: I had problems, similarly to yours, as I had not correct routing + outgoing NAT configuration. It can be also something wrong with the Virtual IPs configuration. Or are you forwarding the firewall ports? Thank you for your answer and sorry for the delayed reply. I was on vaction… I solved the problem by reinstalling pfsense from scratch. I guess something was wrong with my vlan config and stuff because i experimented a lot with different setups and so on plus I started with a double NAT setup and then made the switch to connecting directly through a modem to the internet. So portforwarding is now working as expected. :-) @yarick123: For test purposes I would disable check-sums offloading on all possible physical/virtual NICs. Don't have to do this since I reinstalled pfsense. I'm not touching the proxmox network settings manually anymore.. ;-) Thanks for your help!!

I went back and looked at the WAN rule before I was going to screenshot it and I saw my mistake, under destination I had manually put in the WAN IP address. I changed it to "WAN address" and its working now, so thanks for that. I'm still having issues with getting the VM connected. I've pretty much left everything default with regard to this, I'm not sure if I need some NATing rule? I had a look through the doc you send me, I appreciate that in a normal setup using a VPN would be better but this is purely to separate my VM network from my home network so i'm not fussed about the security hole of having the webui accessible from my home network, i'll never be accessing it from public address space. Thanks