"Recent posts
#1
General Discussion / Unbound DNS hard restarts (cle...
Last post by S1ardust - Today at 09:18:50 AMHi everyone,
I am running OPNsense on my network for some weeks now and I am facing an annoying issue where Unbound DNS performs a hard restart (losing its entire cache and resetting uptime to 0) every time my Windows 11 client disconnects from the LAN.
For reasons, I programmatically disable the network adapter on the Windows 11 client multiple times a day via Disable-NetAdapter.
The Phenomenon & Root Cause
Whenever the client disconnects, the virtualized OPNsense (running on Hyper-V) registers a physical link-loss on the LAN interface (hn1). The subsequent link-up triggers the system script /usr/local/etc/rc.newwanip, which forces a global Unbound restart.
Log output
From "System -> Log Files -> General" (or via clog /var/log/system.log):
Network Topology
You cannot view this attachment.
What I Have Already Tried (Without Success)
To prevent the Unbound restart on link-up, I have already tested the following:
Any advice or pointers would be highly appreciated!
Thank you
I am running OPNsense on my network for some weeks now and I am facing an annoying issue where Unbound DNS performs a hard restart (losing its entire cache and resetting uptime to 0) every time my Windows 11 client disconnects from the LAN.
For reasons, I programmatically disable the network adapter on the Windows 11 client multiple times a day via Disable-NetAdapter.
The Phenomenon & Root Cause
Whenever the client disconnects, the virtualized OPNsense (running on Hyper-V) registers a physical link-loss on the LAN interface (hn1). The subsequent link-up triggers the system script /usr/local/etc/rc.newwanip, which forces a global Unbound restart.
Log output
From "System -> Log Files -> General" (or via clog /var/log/system.log):
Code Select
hn1: link state changed to DOWN (When disabling the client adapter)
hn1: link state changed to UP (When re-enabling the client adapter)
[... followed by rc.newwanip triggering the Unbound restart ...]
Network Topology
You cannot view this attachment.
What I Have Already Tried (Without Success)
To prevent the Unbound restart on link-up, I have already tested the following:
- Tested the setting "Flush DNS cache during reload"
- Prevent interface removal: Activated under "Interfaces -> [LAN]".
- Unbound Network Interfaces: Bound to "All" instead of specific interfaces.
- System Tunables: Set com.opnsense.disable_interface_cycle = 1.
- ...
Any advice or pointers would be highly appreciated!
Thank you
#2
26.7 Series / Re: Bug using Maximize Grid in...
Last post by Monviech (Cedrik) - Today at 09:10:54 AMIt's an issue right now when pages use the virtual DOM and too many log entries should load at once.
The modal moves the already loaded grid instance into itself, but that also means lazy loading new rows which happens when the virtual DOM is used doesn't work anymore.
This is a tougher nut to crack unfortunately, since the virtual DOM requires the grid to be totally responsive with fixed height and width so it can render the scolling. But inside the modal that opens, we want the browser to own the scrolling.
For now you can just go to the next pagination page (e.g. click on 2), and go back to the first (eg click on 1), then it should load all 1000 entries, but it can be slow since no virtual DOM is used.
The modal moves the already loaded grid instance into itself, but that also means lazy loading new rows which happens when the virtual DOM is used doesn't work anymore.
This is a tougher nut to crack unfortunately, since the virtual DOM requires the grid to be totally responsive with fixed height and width so it can render the scolling. But inside the modal that opens, we want the browser to own the scrolling.
For now you can just go to the next pagination page (e.g. click on 2), and go back to the first (eg click on 1), then it should load all 1000 entries, but it can be slow since no virtual DOM is used.
#3
26.1, 26,4 Series / Re: Unexpected error during up...
Last post by franco - Today at 09:09:02 AMThis cosmetic issue was fixed in 26.1.7:
https://github.com/opnsense/changelog/blob/e38c5c2f6d517267f4b6efb8fc7e742521fdf485/community/26.1/26.1.7#L48
So being on 26.1.11 now this won't happen again.
Cheers,
Franco
https://github.com/opnsense/changelog/blob/e38c5c2f6d517267f4b6efb8fc7e742521fdf485/community/26.1/26.1.7#L48
So being on 26.1.11 now this won't happen again.
Cheers,
Franco
#4
26.7 Series / Re: 26.7.3 boot loop on Hyper-...
Last post by Monviech (Cedrik) - Today at 09:06:52 AMI also observed it on the hv_hid since it also loads a kernel module dynamically at that point, so your issue should be the same I assume.
#5
26.1, 26,4 Series / Re: Log to remote logserver us...
Last post by dairysmash - Today at 09:01:12 AMThis topic on logging with TLS and self-signed certificates is fascinating! I've dabbled in network security, and it can be tricky. Have you guys encountered any specific challenges or tips when setting up your remote log server? I'd love to learn more from your experiences!
#6
General Discussion / Re: OPNsense insists that DHCP...
Last post by tangofan - Today at 08:50:35 AMQuote from: Patrick M. Hausen on September 18, 2026, 11:36:36 PMQuote from: tangofan on September 18, 2026, 09:44:58 PMPerhaps it would be a good idea, if at the time of uninstallation of a plugin, there was an option to erase the configuration block of that plugin
- System > Configuration > Defaults > Components
- Select "Services: ISC DHCPV4 [legacy] [dhcpd]"
- Click on "Reset"
- Repeat for DHCPV6
HTH,
Patrick
I was totally unaware that this feature even existed. OPNsense regularly surprises me on the positive side.
Many thanks, Patrick.
#7
26.1, 26,4 Series / Unexpected error during upgrad...
Last post by BigFreddy - Today at 08:41:45 AMHi,
When I was upgrading firewall from version 26.1.2 to 26.1.11, I got the red pop-up window saying there were unexpected errors and to check logs. The upgrade went fine and I haven't had this message pop-up again. I was looking into the logs for a few hours and didn't find any errors around the time when that red pop-up window appeared and I also haven't had any such errors pop-up again.
However, I noticed that during the upgrade in the GUI window there were some conflicts but they were resolved, could this have caused this error to pop-up and if not, were there any issues with the updates between those two versions of OPNsense that could cause this error? I'm just trying to understand why I received the mentioned error.
Thanks
When I was upgrading firewall from version 26.1.2 to 26.1.11, I got the red pop-up window saying there were unexpected errors and to check logs. The upgrade went fine and I haven't had this message pop-up again. I was looking into the logs for a few hours and didn't find any errors around the time when that red pop-up window appeared and I also haven't had any such errors pop-up again.
However, I noticed that during the upgrade in the GUI window there were some conflicts but they were resolved, could this have caused this error to pop-up and if not, were there any issues with the updates between those two versions of OPNsense that could cause this error? I'm just trying to understand why I received the mentioned error.
Thanks
#8
26.7 Series / Re: 26.7.3 boot loop on Hyper-...
Last post by iorx - Today at 08:40:20 AMFinal update for now:
The panic backtrace points to hv_hid_probe() page fault on cpu3, triggered during device_do_deferred_actions() at boot. This is reproducible with 8 vCPU and occurs regardless of OPNsense configuration, a clean default install with no custom tunables shows the same behaviour.
The test VM without RSS tunables also boot loops after repeated reboots, which rules out RSS as the root cause. It is a race condition, consistent with Monviech's 10%/90% observation.
26.7.4 does not appear to address this.
Would it be appropriate to open a FreeBSD-level issue, or add to the existing https://github.com/opnsense/src/issues/297? Happy to provide the backtrace and any additional data that would help.
The panic backtrace points to hv_hid_probe() page fault on cpu3, triggered during device_do_deferred_actions() at boot. This is reproducible with 8 vCPU and occurs regardless of OPNsense configuration, a clean default install with no custom tunables shows the same behaviour.
The test VM without RSS tunables also boot loops after repeated reboots, which rules out RSS as the root cause. It is a race condition, consistent with Monviech's 10%/90% observation.
26.7.4 does not appear to address this.
Would it be appropriate to open a FreeBSD-level issue, or add to the existing https://github.com/opnsense/src/issues/297? Happy to provide the backtrace and any additional data that would help.
#9
26.7 Series / Re: How to reorganize the chan...
Last post by BigFreddy - Today at 08:31:02 AMQuote from: franco on Today at 08:23:05 AMYou can look up the commit, or we can omit them. I don't think omitting adds value, especially if regressions occur.
If it doesn't sound interesting it's probably just that.
Cheers,
Franco
What I had in mind when I was making this post was that it would be a good idea to divide the changelog into more readable sections, in my mind, these three would make more sense: Security, Breaking Changes, Developer Notes then under them, list the changelogs that apply per each section.
#10
26.7 Series / Bug using Maximize Grid in Log...
Last post by BigFreddy - Today at 08:26:51 AMHi,
When I was browsing logs I tried using Maximize Grid which is a new feature and I'm not sure if this is by design or actual bug. What I observed is that if I select in the standard logs window to show me 1,000 entries per page then when I click on Maximize Grid icon, the amount of entries reduced to maximum of 40 entries by default and not the value that I selected, in this instance it was 1,000 entries per page.
Any idea if the shown amount of entries per page in Maximize Grid can be adjusted?
Thanks
When I was browsing logs I tried using Maximize Grid which is a new feature and I'm not sure if this is by design or actual bug. What I observed is that if I select in the standard logs window to show me 1,000 entries per page then when I click on Maximize Grid icon, the amount of entries reduced to maximum of 40 entries by default and not the value that I selected, in this instance it was 1,000 entries per page.
Any idea if the shown amount of entries per page in Maximize Grid can be adjusted?
Thanks
