i am also having issue with carp running kvm/qemu with libvirt.
the devices see each other and choose master and slave respectively but if i turn one off the clients cannot access the virtual ip anymore.
is this fix applicable in my case and if so how do i do it?

I may have figured out the problem with bridging... MAC address spoofing must be enabled on all the Hyper-V vswitches that are being bridged

I came across similar NIC ordering issue some time ago. When I added more than 4 vmxnet3 adapters to the machine, FreeBSD numbered interfaces differently in comparison to VM ethernet adapter order, that issue is described here. When I used E1000 interfaces, the problem disappeared. I had to use workaround script that renamed vmx interfaces in FreeBSD based on their mac address, so that interface order was the same on VM and FreeBSD.

This is however something different. I'm not touching interfaces on the VM, I'm just unassigning/disabling interfaces in pfSense GUI under Interfaces -> Assignments. Though it definitely bears some similarity with aforementioned NIC order bug (meaning that everything is fine with only 4 interfaces on the machine).

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.