Messages

1

24.1 Legacy Series / Re: Ipmi Tool missing After Update to 24.1

« on: July 04, 2024, 05:34:20 pm »

since this topic here let me in the wrong direction for 3hours, i link this for solving the issue

https://forum.opnsense.org/index.php?topic=40240.msg197388#msg197388

Code: [Select]

pkg install freeipmi


2

24.1 Legacy Series / Re: Ipmi Tool missing After Update to 24.1

« on: July 04, 2024, 05:32:05 pm »

Is there any news on this issue? it started on a late 23.x release i think, an update to the latest 24.1.9_4 does not help. for server monitoring this tool is essential for us..

Thanks Kai

3

General Discussion / [Feature] Finegrained restart control for wireguard

« on: September 05, 2023, 04:50:17 pm »

Hi,

we are running HA-Firewall with OpnSense and 4 Wireguard Servers and are pretty happy so far, but as soon as we add a new connection and "Apply" it, all 4 wireguard server get restarted, leading to a disconnect time for all users (for up to <keepalive> seconds).

Is it possible to apply only configs for the WG server which has changes? If not, what would be needed to have this in a feature version of OPNSense?

Thanks

4

German - Deutsch / Re: Nach Update - Fehler beim starten

« on: March 01, 2023, 07:06:53 pm »

Das ist uns heute auch passiert und mittlerweile kann ich zuordnen, dass wir ein update gemacht haben und der Primary Output auf der Seriellen Console lag. Auf der Video Console sah man nur

Code: [Select]

Dual Console: Serial Primary, Video Secondary

und das System schien wegen "Root mount waiting for usbus0" zu hängen, worauf hin wir clevererweise manuell rebootet haben, vermutlich mitten im Update ...

5

21.7 Legacy Series / Re: OPNsense cannot connect via TLS to any server with an Let's Encrypt certificate.

« on: September 30, 2021, 08:02:46 pm »

i think this is a bigger issue hitting a lot of people and should be raised in priority

https://twitter.com/Scott_Helme/status/1443293844292919304

6

21.7 Legacy Series / Re: OPNsense cannot connect via TLS to any server with an Let's Encrypt certificate.

« on: September 30, 2021, 08:01:44 pm »

It also affects ldaps:// connections (!!) and let in our case to broken vpn authentication for our users.

seems the openssl version is the problem. the only thing that helped us for now is to import the ldap servers LE-Certificate into Trust->Authorities. It is then directly trusted by the ssl client and the (assumably broken) chain is not checked.