Topics

hello everyone.

Is anyone else seeing issues with wireguard connections failing between 23.7.6 upon reboot? I have a site-to-site link with a older opnsense router that's on 23.1.11_2 and a roadwarrior tunnel and I'm finding that ever since I did the upgrade, the wireguard connections won't re-establish on reboot. I have to uncheck the peer, hit apply, recheck it and hit apply every time the router is rebooted.

I've noticed the following: on the 23.7.6 side, upon reboot, when I check the new WireGuard Diagnostics page, the tunnels have (none) under the public key heading and the wrong port listed in the table, up until I uncheck/recheck the peer and hit apply. Once I do that, the tunnels behave properly until the next reboot. No changes have to be made on the roadwarrior client side and no changes have to be made on the 23.1.11_2 side for the tunnels to re-establish.

I am positive it was working on 23.7.5 and no configurations changes were made.

thanks!

Perhaps I am misunderstanding the command, but I am trying to create a monit alarm for CPU temperatures, and the number I am retrieving from sysctl is not matching the dashboard by a large margin!

Is there any kind of math I need to do to get the real temp in a script?
Thanks
F

I have a couple of installs of Sensei where it protects the LAGG interface by adding the individual interfaces that are part of the team to the Protected interfaces:

In this case, igb2 and igb3, and it works as expected, handles the VLANS on the LAGG interface, etc...

New install, hardware is slightly different (6 ports instead of 4). Same configuration for the LAGG and interfaces, but the adapters that are part of the LAGG interface do not show up on the available interfaces list to be selected:


Ideas? Suggestions?