Recent posts

#1
General Discussion / OpnSense with 802.11 b/g/n Wi...
Last post by Cobra - Today at 07:18:00 PM
I want to install OpnSense on a MoBo with 802.11 b/g/n Wi-Fi to use as a secondary WAN or, alternatively, as a basic Access Point to which other APs will connect using VLANs.
i3 CPU and 8GB RAM.
WAN1 is a FTTC 100/20 Mb
What do you think?
#2
Hello,

I'm new to OPNsense. I'm trying to set it up for my home, including a small homelab; but I'm getting intermittent failures with DNS lookup from my Mac desktop, and from my phone via wifi.

When I visit webpages from my desktop (wired connection), many sites return the error DNS_PROBE_FINISHED_NXDOMAIN; it ranges from about 5% to 80% of sites I visit. The percentage increases the longer I'm using the web. If I leave the pages open in my browser, then in general, the pages finally resolve, but it takes anywhere from 2 minutes to an hour.

When I browse with my phone via wifi, I also get errors visiting various sites; I can resolve this on my phone by temporarily disconnecting from wifi, accessing the sites via cellular data, and then re-connecting to wifi; those domains then resolve correctly.

My path is as follows:
 - ISP Router <-> OPNsense 25.7 on a Protectli <-> Netgear managed switch (default settings, no VLANs defined yet) <-> iMac, WAP, other computers, etc

It's unclear to me how best to troubleshoot this. I've searched these forums (and googled widely) for DNS_PROBE_FINISHED_NXDOMAIN, DNS lookup, etc; and have found various suggestions about what my settings should be, which I believe I am following.

Any suggestions for a troubleshooting path?

Thank you.
#3
26.1, 26,4 Series / Re: Thin disk / ZFS / Unmap?
Last post by dinguz - Today at 07:09:21 PM
I have found ZFS to be more reliable. With UFS, I experienced disk corruption after power outages and other unclean shutdowns on a few occasions, but never with ZFS.
#4
General Discussion / Re: No IP from DuckDNS and Ded...
Last post by Cobra - Today at 06:52:53 PM
Quote from: JamesFrisch on April 24, 2026, 08:34:17 AMThank you for the heads up. In newer versions of OPNsense, you have to enable the checkbox "Show community plugins".

Although I have to check if that plugin is even needed anymore. Maybe check it this afternoon.

It does not work.
~ # service configd restart
Stopping configd...done
Starting configd.
~ # ./deSEC_DynDNS.sh
./deSEC_DynDNS.sh: Command not found.
~ # ls /usr/local/opnsense/service/conf/actions.d/actions_desecdyndns.conf
/usr/local/opnsense/service/conf/actions.d/actions_desecdyndns.conf
~ # ls
.cshrc          .login_conf    .mailrc        .shrc        .login          .mail_aliases  .profile        .vimrc
#5
26.1, 26,4 Series / Re: This makes me want to cry!...
Last post by meyergru - Today at 06:39:26 PM
The keyword is "webgui" here... as it seems, not even the time being off is present when using SSH.

When the problem occurs only on the web gui, it has to be the client, which means browser or some kind of plugin. I would try another browser first.
#6
26.1, 26,4 Series / Re: This makes me want to cry!...
Last post by alex303 - Today at 05:30:27 PM
Quote from: roohoo on Today at 05:05:55 PMI don't believe it!  I decided that I'd try reinstalling OPNsense as a VM under Proxmox so that Proxmox acted like a sort of Hardware Abstraction Layer.  I even boosted the RAM to 64GB so that OPNSense could have 16GB.

The result:  Exactly the same.  The firewall appears to keep working, with all my network's devices keeping their Internet connectivity, but the webgui is displaying nonsense - with the characteristic 20000+ days uptime (the correct uptime, as displayed in the shell, being 1 hour 45 minutes).

I'm so disappointed as I thought that this might cure my issues - with Linux drivers handing virtual hardware to OPNsense, but it wasn't to be!

That completely rules out the issue with opnsense. Your clients are broken, or something between your clients and opnsense.
#7
Please:

root@opn-dev-02:~ # sysctl kern.boottime
#8
26.1, 26,4 Series / Re: This makes me want to cry!...
Last post by roohoo - Today at 05:05:55 PM
I don't believe it!  I decided that I'd try reinstalling OPNsense as a VM under Proxmox so that Proxmox acted like a sort of Hardware Abstraction Layer.  I even boosted the RAM to 64GB so that OPNSense could have 16GB.

The result:  Exactly the same.  The firewall appears to keep working, with all my network's devices keeping their Internet connectivity, but the webgui is displaying nonsense - with the characteristic 20000+ days uptime (the correct uptime, as displayed in the shell, being 1 hour 45 minutes).

I'm so disappointed as I thought that this might cure my issues - with Linux drivers handing virtual hardware to OPNsense, but it wasn't to be!

#9
26.1, 26,4 Series / Re: NetBird Interface breaks b...
Last post by cookiemonster - Today at 03:45:10 PM
right I see. Sorry no other ideas for now.
#10
I haven't kept up with netboot for freeBSD but in the past it needed to use mfsBSD. Check https://forum.opnsense.org/index.php?topic=25003.msg120021#msg120021 for some pointers.