Although the Redmine Ticket seems to show this fixed back in 2.5.1, your problem seems eerily similar to this one: https://redmine.pfsense.org/issues/11483. Might be something weird going on with the way Hyper-V is presenting the virtual disks ???

I hit this when I tried using ZFS as the file system with expanding disks. It went runaway and eventually caused an outage. I've been meaning to go back and try again with a fixed size disk instead of an expanding one, but haven't got around to it yet, and EXT seems to be fine...

Hi, all on the sameb subnet? If so this should be problem of proxmox. Even if u r not able to 'ping' from unifi controller to pfsense. Are you? Can the unifi controller reach out to the internet? regards, CAT

Hi Livio, have you solved the issue in your case? We are planing to go bare metal in our case.

I think I got it working! I couldn't access the Proxmox web interface anymore either no matter what I tried so I reinstalled Promox entirely. After reinstalling it still didn't work, so I tried again using another subnet in the network configuration during setup, and manually connecting my laptop to that subnet. After that I was able to access the Proxmox web interface again, so I continued following the steps like I did before. I was now able to connect to the pfSense interface too. I think the issue was with DHCP not working yet because the setup of pfSense in the web interface wasn't completed yet; the new subnet I used is the same subnet I used for pfSense (192.168.1.x), so that's probably why I was able to connect now. For now I can't test any further until tomorrow because our switch is in my parents bedroom, and they're asleep now. I did test another laptop and that did immediately get an IP within the subnet, it also was able to connect to the internet.

@alessandro-parreiras check here

@dan-cormack If anyone's still interesting in this topic, here is the brief instruction: Download pfsense ISO Create a FreeBSD x64 VM in VirtualBox with PAE/NX, VMDK hard drive on IDE controller, disable audio and usb; attach the ISO to the VM Boot the VM and install pfsense on the virtual hard drive After installation completed, let the VM start rebooting and power it off Create an OS bucket in OCI and upload the VMDK into the bucket Switch to Compute/Instances/Custom Images and import the VMDK image from the bucket From now you can create an instance from the custom image

@awebster yes, you are right. i have an etherchannel on the switch and nic teaming with IP hash on the esx. the configuration is not a problem; i followed guides for it. Problem might be with the network card's driver in esxi, which although it is supported, it might have some problems.

@kom ok great yeah ive set a dns forwarder for my windows dns server.

Proxmox with a FreeBSD guest Proxmox recommends using ntpd daemon in a FreeBSD client to maintain client real time synchronization. See pve.proxmox. com/wiki/FreeBSD_Guest_Notes and forum.proxmox. com/threads/time-drift-in-windows-7-guest.41268/#post-198848 Real time is set in the guest when it first starts. After which the guest clock drifts with the hosts processor crystal. ntpd is the ntp daemon. See www.freebsd. org/cgi/man.cgi?query=ntpd&apropos=0&sektion=8&manpath=FreeBSD+12.2-stable&arch=default&format=html Configured via /etc/ntp.conf Command line interface ntpq See www.freebsd. org/cgi/man.cgi?query=ntpq&sektion=8&apropos=0&manpath=FreeBSD+12.2-RELEASE+and+Ports 11 minute hardware real time clock update can be enable by adding the line "SYNC_HWCLOCK=yes" to /etc/sysconfig/ntpdate date gives time of day to 1 second resolution Qemu guest agent I think qemu can also sync time between the guest and Porxmox host. Doing so is suggested github. com/aborche/qemu-guest-agent/blob/master/supported_command_reference.md Other virtualization systems such as vmware have time synchronization between host and guest via the agent Time synchronization should be done via only one system otherwise interaction between them decreases time system accuracy. Which mean if an agent and ntpd is used then there would need to be a way of disabling time synchronization via the agent. I'm not sure how to do this. pfsense guest on Proxmox host Given it is probably best to run ntp (chrony) on Proxmox then synch time in pfsense to the Proxmox host via ntpd over the LAN interface. Ideally I would like to do the following but not sure how to acheive that in pfsense Enable ntpd on pfsense but not listening to clients on any interface. Selecting no interfaces in the GUI does the reverse. Disable hardware real time clock update by pfsense. This is done every 11 minutes by chronyd on the Proxmox host. In pfsense the directory structure is different, so I can't goto to /etc/sysconfig/ntpdate and set SYNC_HWCLOCK=no

@nicesub said in Hyper-V server and pfSense setup issues: to specify the wlan .... adapters again Your dmesg logs doesn't mention a wlan NIC.

@patch said in Proxmox zfs install error: I wasn’t sure if both the host and client using zfs was compatible. I suppose you are not using ZFS on the VM data store at all.