Recent posts

#1
General Discussion / Native DDNS Client for Porkbun
Last post by zaphod80013 - Today at 04:39:01 AM
Hello

Hope I'm posting this is the right place, only joined the forum to drop this piece of code for anybody to use. While evaluating OPNsense as a replacement for PFSense I couldn't find a native DDNS plug-in for Porkbun so I rolled my own; code at https://github.com/zaphod80013/opnsense-ddns-porkbun)or search github zaphod80013 opnsense-ddns-porkbun. Since OPNsense didn't solve the network prefix translation issue I was seeing in PFSense I've no reason to switch at this time but the code may be useful to someone. 
#2
Need to take a look at your squid configuration file: /usr/local/etc/squid/squid.conf
Could you post it on the forum?
#3
Hi:
I am experiencing an issue with Development ver (latest) and doing an initial dialogue and setup.

Running Windows 11 Dev. Insiders Preview (26H2)

OPNSense 26.7.1 Devel. (Latest)

Strange issue happening; after I go through initial setup with installer wizard, and initial ZFS install... Basics and no frills services are setup and initial root password is set.  I also setup an additional backup admin user; and reboot.

Everything works as expected and installed; but a short period after install; both users (root and backup) accounts are now inaccessible and will not login.  I have tried reinstalling, with same result.  I can also recovery boot and reset root password with apparent success; only to have root / password deemed inaccessible and the only way to login is to do recovery and manually reset to factory with wizard reset.  I am really puzzled as to what could be happening; because I can't see any apparent connection to reason accounts are inaccessible.

Any insight or guidance would be appreciated... I don't really know where to start.
#4
26.1, 26,4 Series / Re: 26.1.7_2: issue with ACME ...
Last post by Creat - Today at 02:48:40 AM
Did this ever get resolved or anyone find out the actual cause?

My problem is that I did setup the (new) websocket cert push, and I know it worked fine as I swapped over to that cert. Now it needed a renew, and for some reason it failed to push, showing the same symptoms as described here.

I do NOT want to run letsencrypt on the TrueNAS box as well. That's the whole point of having it on the router/firewall.

To be more explicit:
The only normally accessible error in the log is this:
AcmeClient: AcmeClient: The shell command returned exit code '1': '/usr/local/sbin/acme.sh ...When manually running that command that fails, I get the same errors the others posted (TrueNAS is not ready. and all that). to my knowledge, the TrueNAS API also doesn't need (or allow) any configuration. I'm currently still on 25.10.3.1, but .4 seems available.

So what gives?
#5
Well,
Try a manual install. Does it take or fail?

I think early ucode loads can be blocked by a bios/eufi ucode process because the 1st loading was still in ioctl which is a kernel operation, and loader.conf was blocked at that point. 100% possible.
#6
26.1, 26,4 Series / Re: Degraded Speed Ghost
Last post by pfry - Today at 12:14:44 AM
Quote from: juicemain on June 20, 2026, 11:44:27 PM[...]I tried the Protectli Vault FW2B, and wow.  Not good performance.[...]

Just a note, that's not surprising when compared to your ThinkCentre M720 or OptiPlex 7070 SFF (even assuming minimal configurations for those two).

Did you check ARP on your equipment (not just presence, but correct MACs)? Again, Linux-based devices would likely be unaffected.

Misconfigured ISP equipment is a distinct possibility as well, but getting an actual tech to look at it is practically impossible these days. (Don't think AI will improve this, as it's a management/policy issue, which will not change.)
#7
Zenarmor (Sensei) / Re: updating to 2.6 checking f...
Last post by sy - June 21, 2026, 10:50:28 PM
Hi,

Sorry to hear that. Please share the repo conf file. Run the commands "cat /usr/local/etc/pkg/repos/sunnyValley.conf" and "pkg update -f", then share the output.
#8
26.1, 26,4 Series / Re: WAN Interface speed duplex...
Last post by stumper - June 21, 2026, 10:19:38 PM
Problem solved - turned out to be an electrical issue and not equipment or configuration related. Moved the cable modem and firewall appliance to a different outlet and everything working again. Contacted an electrician to investigate and fix.

Thank you all for the input and suggestions
#9
26.1, 26,4 Series / Re: Update issues when upgradi...
Last post by Patrick M. Hausen - June 21, 2026, 06:58:55 PM
Production is not working because FreeBSD is not supported in Hyper-V. Only Microsoft can change that. Standard seems to have the issues you describe - again IMHO only MS can change that.

You could shutdown the VM at night, take a snapshot, boot up again.

Or schedule configuration backups to Nextcloud, git, SFTP, ... your choice really. And not rely on VM snapshots for backup.

Also there is a perfectly capable snapshot mechanism within OPNsense if you install with ZFS. So if I was to insist running an u supported guest OS in my hypervisor I would at least not plan with any of the advancec hypervisor mechanisms like snapshots to be working but use different means.

HTH,
Patrick
#10
26.1, 26,4 Series / Re: Update issues when upgradi...
Last post by tverweij - June 21, 2026, 06:42:27 PM
Quote from: tverweij on June 21, 2026, 06:33:53 PMI use production - needed for backup.
But I also tried Standard - just made a standard snapshot by hand and removed it again.

Both production as standard snapshot causes the errors to be displayed in the OpnSense VM.
No difference that I can see.


Wait a minute.
I just disabled the option "Create standard checkpoints if the guest does not support creation of production checkpoints".
And now it can not create a checkpoint anymore.

This means Standard checkpoints are used - Production checkpoints are somehow not supported by the OpnSense VM.