"
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 ...
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 ...
