Hi all
I had a shot interruption on a physical swtich which is connected to a Hyper-V host. On the Hyper-V host, there is a OPNSense running (since years).
After the connection went up again, the OPNsense was unable to recover from the short outage and the box stayed completeley disconnected while throwing the error "arprequest_internal: cannot find matching address" The only way to bring back the OPNSense back was a reboot!
I have recreated the virtual switch on Hyper-V and removed Zenarmor just to isolate the problem. No success
Someone experience the same? Any ideas?
yes, same here
using proxmox and opnsense and get those messages too
works flawlessly on other servers
Wierd... never have seen something like this. Maybe related to FreeBSD?
The main problem ist, that the failover also not properly work. Fail over works but it tries to fail back and then loosing connection completely
Just happened again. This is a serious issue! The only way to solve this is to reboot the VM..
same here. my opnsense vm suddenly lost configuration and i am unable to restore it because it throws mentioned error
proxmox 8.1.4
Quote from: wntrmt on March 23, 2024, 02:32:05 PM
same here. my opnsense vm suddenly lost configuration and i am unable to restore it because it throws mentioned error
proxmox 8.1.4
[mention]wntrmt [/mention] Lost config? This seems to be something else.
I think i cold solve the ,,arp" Problem deactivating the hardware acceleration features on the interfaces. Now opnsense survives a quick disconnect from the network again.
it seems to me like it could not start properly and reverted to defaults because of underlying issue. i will check hw acceleration, thanks for sharing
Just realized this is pretty necro but I have seen this and maybe solved it on my end. Was the OP using any reverse proxies to access it?