![]() The fix every time was just rebooting pfSense. If I did an ifconfig down then up on the vtnet1, the LAN adapter, pfSense would be able to ping the hypervisor again, as mentioned in the Netgate docs, but the host still couldn't use pfsense to connect to the WAN. pfSense could access the WAN just fine, nothing in the logs, but it also could not ping the host, albeit with a more informative message: " ping: sendto: No buffer space available". I'd SSH into pfSense, nothing in the logs. But the hypervisor couldn't ping pfSense over the LAN, much less access the WAN. I'd IPMI into the hypervisor and see nothing in the logs. Since I started running on this new install with production traffic, pfSense would stop relaying traffic to/from the hypervisor every few minutes. pfSense got a fresh install (I did not move the old VM over to the new hypervisor install) The one thing that changed is now Proxmox is installed on ZFS (native proxmox install) intead of RAID 1. Proxmox version has been (since released) the same as it is now, and pfSense had been (for months) the pfSense+ version 22.x (and before that pfSense CE). I have had pfsense working fine on this same HW for years. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |