Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - mgrunwald

#1
24.1, 24.4 Legacy Series / Kea Subnets
April 26, 2024, 11:41:28 AM
I was starting to look into KEA but I wondered about something. When creating a new interface I'll define an IP address in CIDR notation, which also defines the network size. This information will then transfer over to the ISC DHCP server. I don't need to define subnets because they are defined by my static IP configuration from the Interface creation. Why doesn't this information transfer over to KEA like it did to ISC?
#2
I am not sure this was mentioned before but https://desec.io no longer new registrations for DynDNS.
For the German speaking audience I can highly recommend https://ipv64.net/
Many texts on the website are English, but someone not speaking German might have problems understanding everything
#3
The update from 23.7.12_5 to 24.1 breaks my HAProxy Let's Encrypt setup. I have multiple wildcard certificates in the ACME client and I use a CloudFlare DNS challenge. After the update the first certificate in the list is used for every connection and I get a NET::ERR_CERT_COMMON_NAME_INVALID error. Before the upgrade when I made a connection to a domain that was not covered by the first cert, the correct one was used. What is going on?

edit: after some troubleshooting I think I identified the problem and created a GitHub issue: https://github.com/opnsense/plugins/issues/3779
#4
Thank you very much for the tutorial! This worked great for me until I upgraded to 24.1. This broke my setup and every connection uses the first cert in the list even if this is for a different domain. I get the NET::ERR_CERT_COMMON_NAME_INVALID error