Messages

1

24.7 Production Series / Re: Stalled upgrade to 24.7.6 shutting down crowdsec

« on: October 10, 2024, 07:31:33 pm »

From this thread: https://forum.opnsense.org/index.php?topic=43309.0

Open a terminal command line and then

killall -9 crowdsec

2

24.7 Production Series / Re: Android devices cannot connect to the Internet after upgrading to version 24.7.6

« on: October 10, 2024, 06:49:55 pm »

I've been having issues with Android devices connecting over IPv6 since the "FreeBSD security advisory" patch and the back and forth with reverting it.
You may want to see this thread, it may be relevant: https://forum.opnsense.org/index.php?topic=42556.0

3

24.7 Production Series / Re: Stuck at update 24.7.6 (no more)

« on: October 09, 2024, 10:12:42 pm »

Ran into the same issue, Crowdsec held up the update and was unable to end just that process.
Rebooted and resumed the update after disabling Crowdsec and now all seems to be running correctly.
If you have not yet updated, try disabling Crowdsec before you update.

4

24.1 Legacy Series / Re: 24.1 - DHCP server moves to KEA - implications?

« on: January 31, 2024, 10:15:48 pm »

Hello all,
Upgraded from 23.7.12 to 23.7.12_5 and then immediately to 24.1_1.
Running 4 physical interfaces with separate networks on each, 2 wan, 2 lan with DCHP service.
Switched from ISC to Kea DHCPv4
Transitioned to the Kea DHCPv4 service was simple but seems to be an all or nothing issue.
Attempting to get Kea listening on interface 1 would not work with ISC DHCPv4 listening on interface 2 (seems the ISC DHCPv4 server locks the port on all interfaces).
Once I had both subnets defined (you can do them separately for clarity) and disabled the ISC DHCPv4 instances Kea was able to start as per the logs and as per GUI.
I would be happy to test the Kea implementation further.
Thanks

5

23.7 Legacy Series / Re: Upgradethread 23.1.11_1 to 23.7

« on: August 01, 2023, 01:28:59 am »

Completed the upgrade from 23.1.11 to 23.1.11_1 with no issues. The upgrade from 23.1.11_1 to 23.7 seemed to proceed with no issues, but after the update was complete internal machines had no internet access. I could no longer access the firewall with the FQDN but could access it directly via IP address. For some reason unbound was not started. Going into the configuration the check box to enable it was not checked and some of the other required settings were missing. Enabled unbound and restarted the service and only other minor issue was a complaint about a logging database missing (I had OPNSense create what it wanted). Has been running fine since.
Setup includes two wan interfaces and two lan interface with a firewall rule for gateway fail over.