PfSense on esxi 6.7, can get it to work propperly.
-
Sorry,
The WAN is a wrong setting. this is the right setting for the WAN.
It's the WAN of the vmnetwork of the onboard NIC of the motherboard,
-
and here are some screenshots.
you can see that the ubuntu instalation on ESXI is working perfectly with internet access.
it running on the DHCP lease of 10.0.0.X.You can also see that my Windows 10 laptop and my Synology NAS wich are connected trough LAN cable on the NIC are not getting the right IP address. so there is no DHCP.
https://imgur.com/a/ZDUSXnm
-
Are both, network adapter 1 and 2, realteks?
EDIT 1:
Just saw that wan and lan are Realtek, but VMNetwork is Intel.Need to look again ...
EDIT 2:
At the time it works, does your WAN (Network Adapter 1) is set to VM Network or WAN?
-
It only works when i set the WAN on VM Network.
When i set it on WAN it wont work. -
Then it is related to the realteks. You somehow need to validate whether they operate properly in ESXI at all. Another option could be, as mentioned by @kiokoman, to change to vmxnet3 in pfsense-VM-settings of ESXI.
-
yeah in any case realtek card are never a good choice for this stuff
-
ok.
In the meantime i have tried to run PfSense directly installed on a SSD.
That is running fine, and working woth both the INTEL nic for the WAN and the realtek as the LAN.The devices that are attached trough a LAN kabel are getting 10.0.0.X and internet access,
When i tried it with windows 2019 its working perfect without a problem. So i think i need to consider to leave ESXI for what it is. or try a different hyperviser OS.i only want to use it for:
1x windows server machine
1x firewall machine
2-3 linux machines.Any thought?
-
change that realtek card to some intel they are cheap on ebay / amazon after all
-
Exactly what I would recommend as well. It would cost only a few bucks and will work right out of the box with ESXI. Otherwise you need to spend countless hours or days to get into another hypervisor. Do the math to your liking :)
-
Thank you both for the help :) i will buy a Intel card ;)
I just found one of these: https://ark.intel.com/content/www/us/en/ark/products/184824/intel-ethernet-network-adapter-i350-t4-for-ocp-3-0.html for €20 euro.
Will this one work?
-
With ESXi have you tried putting the LAN vSwitch and Port Group into promiscuous mode ?
-
ok so, i bought this https://ark.intel.com/content/www/us/en/ark/products/184824/intel-ethernet-network-adapter-i350-t4-for-ocp-3-0.html inserted it in the ESXI and booted up. It works perfectly.
So now it is running and working like this:
Fiber optic > Ubiquiti USG router WAN > Ubiquiti USG router LAN > network port NIC ESXI WAN > network port NIC ESXI LAN > Network switch and accespoint in the house. ( 10.0.0.X range. ) this is working perfect.
But i want to remove the Ubiquiti usg router so i can setup the fiber optic directly into the WAN port of the NIC of the ESXI.
so i'm working with T-Mobile here in here in the Netherlands. and i have added the VLAN 300 for internet into the PfSense on the interface of the WAN port of the NIC:
Under interfaces > assigment i have put the new VLAN300 into the WAN:
But i dont get a IP from the DHCP server of my ISP provider.When i set it back on the normal settings, everything is working perfect and i get a 192.168.1.2 from the Ubiquiti USG.
-
under esxi did you set the vswitch to vlanid 4095 ?
-
So i need to edit this one:
This is the nic port that is comming from the fiber optic.And can you tell me WHY i need to add VLAN 4095?
-
This is a specific of ESXI. If empty, VLAN are NOT supported. 4095 allows ALL VLAN numbers from the VM. I still get confused about VLAN, tagged, untagged, etc. But this should work,
-
indeed 4095 means that you set your vswitch as a trunk port letting any vlan pass through
-
Yes, this did the trick :)
-
so after a few day's working perfectly.
it now randomly stops working.In the PfSense VM i see this:
When i reboot the VM everything works again.
What can this be? -
try to reinstall open-vm-tools
maybe do a fsck also -
i have reinstalled the open-vm-tools and nothing changed
what you mean by fsck?And what about the new update?
i'm now on:2.4.4-RELEASE-p3 (amd64)
built on Wed May 15 18:53:44 EDT 2019
FreeBSD 11.2-RELEASE-p10
