Topics

After several months of using opnsense and a couple of firmware updates to it, I still get this issue:

https://forum.opnsense.org/index.php?topic=41676.msg204737#msg204737

I just experienced it today. Is this not yet fixed?

Here are some logs that triggered today:

https://gist.github.com/kevindd992002/bd55652b9847ca0af03e0d3c24f45957

The WAN gateway never went online until either I restarted the VM or manually renewed the WAN connection in the opnsense GUI.

I have OPNsense 24.7.11_2-amd64 installed in a Proxmox VM and am wondering if it has ZFS trim and scrub scheduled by default? Or do I still need to add both tasks as a cron job?

If they're not enabled by default, why? Is there a reason we don't want these two?

After an Internet outage, my WAN gateway does not go back up until I disable and re-enable it in the opnsense GUI. This has happened twice already and I see a lot of these in the logs since the Internet went down:

2024-07-23T08:32:34   Warning   dpinger   WAN_GW 8.8.4.4: sendto error: 65   

I don't have any custom time settings in the gateway. The only custom setting I have there is the monitor IP (8.8.4.4) and everything else is at their default.

Thoughts?

Yesterday at around 12PM GMT+8, my whole network at home went down. I wasn't at home until now so I thought it was just an ISP issue. But then I checked my opnsense VM (proxmox hypervisor) and saw that opnsense was rebooting in an endless loop as shown here:

https://youtu.be/EovhQ0KbWnc

I forgot which version I am on but I last updated within a month or so, so it's pretty recent. I have cloud backups to my Google drive and for some reason the latest backup i see there is July 24, 2024. I don't remember making any changes since then so I guess that's fine if I need to restore from backup.

However, before restoring, I want to know what caused the issue in the first place so I'm good with troubleshooting this. I don't have a lot going there aside from having the AdGuard Home plugin running as a plugin and a couple of other plugins that I'm not yet actively using.

Thoughts?

After an Internet outage, my WAN gateway does not go back up until I disable and re-enable it in the opnsense GUI. This has happened twice already and I see a lot of these in the logs since the Internet went down:

2024-07-23T08:32:34   Warning   dpinger   WAN_GW 8.8.4.4: sendto error: 65   

I don't have any custom time settings in the gateway. The only custom setting I have there is the monitor IP (8.8.4.4) and everything else is at their default.

Thoughts?

I just installed the latest (24.1.8) of opnsense in a Proxmox VM with the CPU set to Host for the VM. My host's CPU is an i3-10100. So I tried "None/ACPI" and "Intel" in the Thermal Sensors setting under Miscellaneous to no avail. Any thoughts?

@migugmail , can you confirm what exactly does the "Primary DNS" setting in the AdGuardHome plugin do when AGH listens at port 53? I don't see any documentation about it and the single line help line there is not that helpful.

I just transitioned from pfsense to opnsense and wondering if this DNS issue is solved in opnsense? When a new device goes through the DHCP process and I have "register DHCP leases" checked in Unbound, does Unbound restart itself? This has been an issue with pfsense until now and I just kept the option disabled which means I can't resolve DHCP devices.