Messages

Great thank you both for the clarification!

Who says where that it is deprecated?

Maybe its one of the package dependencies?  On installation of the plugin on 25.7 I get the following:

Message from libxslt-1.1.43_1:

--
===>   NOTICE:

This port is deprecated; you may wish to reconsider installing it:

unmaintained with multiple unfixed security vulnerabilities.

It is scheduled to be removed on or after 2025-09-12.

Greetings!  What is everyone using for lets encrypt certs these days?  I have been using the os-acme-client but I noticed that its deprecated now and set to be removed after 9/12/2025?  So what is the recommended solution for this purpose moving forward?  TIA

EDIT:  Thank you for the replies and for clarifying that this is not applicable to OPNsense

Sorry pulling this one out from the archives.  I ran into same issue, same backstory:

Installed ZenArmor early on for testing then removed it.  After upgrading to 25.1 I started seeing errors referencing mongodb telling me to submit a bug report.

pkg list | grep mongo

Listed both mongodb40 and php82-pecl-mongodb

They are also viewable in the packages list when you filter for mongo

pkg remove for both has resolved the issue for me

In reading the documentation I was expecting to be able to look at stats from the last 7 days when I go into the reporting for unbound DNS.  The only options I see are for the last 24, 12, or 1 hour.  Is there a setting that I am missing that will allow me to see the full week in reporting?

TIA

Thank you for your reply.  I own the modem and it is several years old.  Its an Arris SB6190.  I logged into it and cleared the logs.  No reboot last night so Xfinity must have been having some issues in the area (we are pretty rural here).

Whatever the issue was it would appear it was on the Xfinity side because I read that error is caused by power/signal issues. It's just really odd that it was rebooting exactly 24 hours apart.

My guess would be DHCP as well. Out of curiosity, I searched to see if there was a way for you to see how long the lease was for your DHCP address on the WAN interface. I did find the following that might help you troubleshoot it a bit more: https://www.reddit.com/r/opnsense/comments/xphlfp/is_there_a_way_to_check_wan_uptime_or_dhcp_lease/

What I've seen on a DHCP WAN renewal is that the WAN interface changes to the private IP on your modem (for my brand it's 192.168.100.1) and then eventually changes to the assigned IP from your ISP. I didn't dig into your log enough to see if that is what was happening.

If I have block private address enabled on WAN would that cause an issue?  My CM is doing the same thing based on the logs.  Its giving the 192.168.100.x addressing and since that is a private address its blocked on the WAN.  From the logs it appears as if the ethernet cable from the WAN is being unplugged.  It shows DOWN and then 6 seconds later shows UP.  Then 5 seconds later the dhclient throws an error "connection closed".

When I login to my Arris CM I see this in the event logs around the same time:
Thu Jan 01 00:01:44 1970   3   No Ranging Response received - T3 time-out;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.0;

It looks like my cable modem is rebooting.  Uptime on the web interface for cable model shows uptime of 16h.

My guess would be DHCP as well. Out of curiosity, I searched to see if there was a way for you to see how long the lease was for your DHCP address on the WAN interface. I did find the following that might help you troubleshoot it a bit more: https://www.reddit.com/r/opnsense/comments/xphlfp/is_there_a_way_to_check_wan_uptime_or_dhcp_lease/

What I've seen on a DHCP WAN renewal is that the WAN interface changes to the private IP on your modem (for my brand it's 192.168.100.1) and then eventually changes to the assigned IP from your ISP. I didn't dig into your log enough to see if that is what was happening.

If I have block private address enabled on WAN would that cause an issue?  My CM is doing the same thing based on the logs.  Its giving the 192.168.100.x addressing and since that is a private address its blocked on the WAN.  From the logs it appears as if the ethernet cable from the WAN is being unplugged.  It shows DOWN and then 6 seconds later shows UP.  Then 5 seconds later the dhclient throws an error "connection closed".

When I login to my Arris CM I see this in the event logs around the same time:
Thu Jan 01 00:01:44 1970   3   No Ranging Response received - T3 time-out;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.0;

It looks like my cable modem is rebooting.  Update on the web interface for cable model shows uptime of 16h.

Yes that's what appears to be happening.  Thanks for the link I will try to collect some more data.

Greetings all,

I have a newly installed OPNsense 23.7.10_1 installed on a protectli FW4B with 8/120.  The system works excellent except for one issue.  My WAN interface seems to be flapping at exactly the same time every 24 hours and I am trying to figure out why that is.

This is what I see in my logs.  The connection issue resolves on its own within 1-2 minutes however I would prefer that it not go down like this of course.  I am using XFINITY with an ARRIS modem.  I am thinking this has something to do with DHCP and it first tries to get a private address before its assigned the public address according to these logs.  I do have private address blocked on WAN.

Any ideas how to fix?  TIA.