Recent posts

#1
opt2 is an internal identifier not a real interface name (would expect ovpn1 or something)

Maybe there is something wrong still, can you open an issue on github how to reproduce?

https://github.com/opnsense/core
#2
26.7, 26.10 Series / 26.7.5 SNAT on OpenVPN client ...
Last post by tja - Today at 07:35:23 AM
hi,

yesterday we installed a complete new 26.7.5.
this is a remote site which connects to an existing OpenVPN hub.
the client sites are using "Outbound NAT" as we dont want the hub to have to know/route all these remote networks.

we tried to use "Source NAT" to rebuild the functionality under the "new firewall" regime but after much effort we are unable to see translation happening.
as we dug deeper we found that there seems to be no valid nat rule generated even as the UI happily swallowed our input.

if we grep /tmp/rules.debug the nat rule is there but commented out:
# nat on ##opt2## inet from (vtnet0:network) to 10.10.10.0/24 -> opt2ip port 1024:65535 # openvpn XXX SNAT
a test rule that swaps the openvpn interface with wan appears to be valid:
nat on vtnet1 inet from (vtnet0:network) to 1.2.3.4 -> (vtnet1:0) port 1024:65535 # wan XXX TEST
i'm sure we did something wrong and our current understanding of the new firewall regime is lacking.

can someone point me in the right direction ?

tia,tja...
#3
deleted. posted by mistake...
#4
26.7, 26.10 Series / Re: Dashboard graph widgets be...
Last post by oc - Today at 05:25:16 AM
Quote from: yunan777 on November 17, 2026, 10:33:44 AMThe CPU and traffic graph on dashboard widgets display no data after updating to 26.7.9. But in reporting -> traffic, the graph works well.
Works well for me, updated to .9, then .9_1, then .9_3.

Can you please try to reproduce the issue in another browser/on another computer?
#5
General Discussion / Re: DNS wildcards in Alias (Ho...
Last post by oc - Today at 05:20:05 AM
Hallo Martin Seener,

Thank you for putting the work into creating this plugin! I really hope it'll make it into the core sometime soon.

I do have a question though - on your website you are mentioning this model:

client ──DNS──▶ AdGuard Home / Unbound ──▶ Wildcard Aliases ──▶ upstream resolver

Which makes me wonder - would your plugin necessarily have to forward the lookup to an external upstream resolver? If currently that is  the case, is there any way to insert it before Unbound, and let Unbound be the actual resolver? Or could at least the plugin refer ONLY its own resolution requests to an upstream server, and let Unbound take care of all client resolution (most of which isn't in most case alias-based)?

Danke,
OC
#6
26.7, 26.10 Series / OPNsense IPsec VTI can’t esta...
Last post by volga629 - Today at 03:44:21 AM
Latest release IPsec is not establish VTI based tunnel, prior update everything was working  with BGP.

Versions
OPNsense 26.7.9_3-amd64
FreeBSD 15.1-RELEASE-p6
OpenSSL 3.5.9

As you see no ipsec outbound packet from firewall, where are shunt policy is installed.

Second tunnel is not establish connection at all.

On  cli

root@fw01:~ # swanctl --list-pols
no files found matching '/usr/local/etc/strongswan.opnsense.d/*.conf'
bf665be7-7931-4993-9c03-50d54c1f5c6a/2c9e658d-075b-478d-832e-118dfc95d592, reqid 20, TUNNEL
  local:  0.0.0.0/0
  remote: 0.0.0.0/0
da254f91-ea8e-49ef-b1ba-c1727fa06ec9/a9d737db-caa5-46a3-abd7-23b4a655c683, reqid 10, TUNNEL
  local:  0.0.0.0/0
  remote: 0.0.0.0/0
root@fw01:~ #
root@fw01:~ #
root@fw01:~ # swanctl --list-sas
no files found matching '/usr/local/etc/strongswan.opnsense.d/*.conf'
da254f91-ea8e-49ef-b1ba-c1727fa06ec9: #1, ESTABLISHED, IKEv2, d0d18c586249fe6e_i bd4db6166f5b61ff_r*
  local  'local public ip ' @ local public ip[500]
  remote 'remote public ip' @ remote public ip[500]
  AES_GCM_16-256/PRF_HMAC_SHA2_384/MODP_2048
  established 2383s ago, rekeying in 11269s
  a9d737db-caa5-46a3-abd7-23b4a655c683: #3, reqid 10, INSTALLED, TUNNEL, ESP:AES_GCM_16-256
    installed 2383s ago, rekeying in 1002s, expires in 1577s
    in  c40d2ec1, 137280 bytes,  4644 packets
    out c7f55d71,      0 bytes,     0 packets
    local  0.0.0.0/0
    remote 0.0.0.0/0
root@fw01:~ #


#7
26.7, 26.10 Series / Re: tailscale interface down (...
Last post by willj8823 - Today at 01:56:38 AM
I posted about this back in July.

https://forum.opnsense.org/index.php?topic=52552.0

In my case, tailscale was and is working fine. It is just that the icon is red like the interface is down.
#8
26.7, 26.10 Series / Re: After upgrade to OPNsense ...
Last post by zz00mm - Today at 01:47:37 AM
All,
     I had the same issue with Cloudflare. When I updated the API token via the GUI, the account.conf file wasn't updated. Manually updating the file and recreated the certificate was successful.
     I wonder what triggers updating the account.conf file. When I modify the API key via the GUI it doesn't update the file.

     I have an additional domain via dynu and it's not updating either when I modify the API/secret.

zz00mm
#9
Virtual private networks / New OpenVPN Setup Issues
Last post by Kitdrewne - November 17, 2026, 11:56:15 PM
I just installed a new firewall running OPNsense and have everything working well across the network. I went through and configured an OpenVPN server on it, but whenever I try connecting the client just hangs and never connects. Checking the logs, I'm getting these three lines each time I try connecting:
Code (openvpn.log) Select
2026-11-17T14:15:32-07:00 Error openvpn /usr/local/opnsense/scripts/openvpn/ovpn_service_control.php: The command </usr/local/sbin/openvpn --config '/var/etc/openvpn/instance-3e920d50-f798-456e-ac8a-27687fb8f96c.conf'> returned exit code 1 and the output was "2026-11-17 14:15:32 DEPRECATED OPTION: --persist-key option ignored. Keys are now always persisted across restarts."
2026-11-17T14:15:32-07:00 Warning openvpn_server1 Use --help for more information.
2026-11-17T14:15:32-07:00 Error openvpn_server1 Options error: --local addresses must be distinct from --ifconfig addresses

On the client side, I tried removing the --persist-key option from the config, but it's still not connecting. I tried that while I was off-site though, so I'm not yet able to confirm how/if the error changed. Here are my configurations below:

Firewall (relevant entries)
RuleOriginVersionProtocolSourcePortDestinationPortGateway
OpenVPN (Group)*IPv4******
WAN*IPv4UDP**WAN AddressOpenVPN (Group) network*

Code (OpenVPN Instance) Select
Role: Server
Protocol: UDP
Port Number: 1194
Bind Address: 10.18.32.1
Type: TUN
Server (IPv4): 10.18.32.0/24
Topology: Subnet

TLS static key: [Set]

Authentication: Local Database
Strict User/CN Matching: Yes

Local Network: 192.168.2.0/24, 192.168.1.0/24, 192.168.20.0/24, 192.168.30.0/24, 192.168.40.0/24
Remote Network:

I'm using the single file option when exporting from OPNsense and have tried connecting both with KDE Network Manager under CachyOS and Viscosity on macOS with the same results. It's been a little while since I set one of these up, so I was referencing the documentation as well as another OPNsense instance I had configured previously elsewhere while setting this up initially.


Any advice would be much appreciated!
#10
General Discussion / Re: netgate freebsd performanc...
Last post by Greelan - November 17, 2026, 11:52:13 PM
Haha, I noticed the same release notes :)

The associated issue is that as far as I can tell the latest CE release came 3 months after the previous, which itself was nearly a year after the one before that. So users are stuck with "potential" issues for possibly extended periods.