pfSense just needs to see link down by whatever method your hypervisor allows.

You could edit the post title which is in your first post and prepend it with [SOLVED] or [RESOLVED], depending on your preference.

Thanks for your help!

In my case it worked after I deleted all the partitions as in the guide and then created a new one (vtbd0s1) with partition vtbd0s1a having 24 GB and mounted in /

Screenshot_5.jpg

Like @KOM said, most Linux flavours use /etc/resolv.conf for DNS resolution. You can manually set a static DNS entry in there by specifying the correct nameserver as the pfSense box. chattr +i /etc/resolv.conf should prevent changes to it being made on reboot.

It has been a while but if I remember correctly you need to tweak Xenserver to fix that problem. I think these are the correct instructions, at least the ones I used, to address that problem. Running pfSense in XenServer

It would be like this, though I have never tried that in GCE the same thing applies in AWS or Azure:
https://cloud.google.com/vpc/docs/create-use-multiple-interfaces

Steve

@eiger3970 said in No WAN IP:

I connected the bridged ISP modem’s LAN cable to another device and Internet works.

One more thing to check : the WAN NIC on the pfSense device.

Invert LAN and WAN during setup - console access - and retest.

A pfSense can be hookup up after any (router or modem or something else) that has a DHCP server on it's LAN.
pfSense, using DHCP client should and will receive an IP.

Thanks for taking your time, appreciate the help.

@l0rdraiden Hi,
yea found a solution for virtualizing pfsense. I switched from kvm / esxi to XEN and its working perfectly now.

Just a follow up here in case anything in the future experiences issues like this.

I was able to resolve this by changing two settings. First, I had to set the ESXi host power management to High Performance, this was defaulted to Balanced. This stopped the clock throttling on the CPU, which in my case is a very low power 10W SOC, I did not notice an increase in power usage but it helped to stabilize the responsiveness of the ESXi host on this low powered system.

The second item that I changed was to edit the pfSense VM, go to advanced options, and set the latency sensitivity to High. by default, the latency sensitivity is set to Normal. A High setting means that the CPU and memory need to be reserved for the VM to power on, so ensure that your host has enough resources to support this.

Changing the two settings above resolved the latency differences that I was seeing. I am now getting identical latency readings between bare metal and a virtualized pfSense VM with NIC passthrough.

I tested this method with 2.4.4p2, 2.4.4p3, and current versions of the 2.5 development images. All experienced the same successful outcome in terms of reducing latency to that of a bare metal system.