Messages

Yes exactly :-D The RJ45 is the WAN device and a USB2RJ45 adapter is the LAN device. It's just for my home setup, so nothing critical ;-)

Thanks for your powersupply hint! I checked it, it is an original power supply. And the commands to check under-voltage showed no errors. But i will continue to monitor it. Thanks!

ok, it turned out that for some reason i don't understand the network device eth1 went down on Pxvirt/Proxmox level. Now i always need to restart the networking.service after a reboot of the RaspberryPi to bring up eth1 (Autostart is set but seems not to work).

The "funny" thing and the reason why i didn't look in this direction was that i didn't touch this device. I changed the driver of the WAN port of OPNsense which is eth0 on Pxvirt/Proxmox, not eth1.

Well, it's working so far again after more or less a day of troubleshooting, reassigning network devices and new installation (the good thing on hypervisors ist that one can work and test with clones and keep the original untouched), i hope i can find out why eth1 now is making problems ...

OPNsense as VM on Pxvirt and RaspberryPi4. Worked fine until up to version 25.7 or 26.x i couldn't recall exactly. Then OpenVPN connection to an external VPN-Server started being very slow and with packet loss.
To solve this problem ChatGPT gave me the advice to change the driver of the WAN interface vmbr0 on the OPNsense VM (eth0 on Pxvirt) from VirtIO to Intel E1000. After changing the driver to Intel E1000 i couldn't connect to LAN interface vmbr4 (eth1 on Pxvirt) anymore. Changing back the driver to VirtIO didn't help.
I can access the firewall on WAN prot though.

Any ideas on what could be broken?

Thanks!

Andino