Recent posts

#1
The code only cares for a prefix existing in this file:

https://github.com/opnsense/core/blob/8b88393932c94b7dafea941803ae0fe34f966888/src/opnsense/mvc/app/library/OPNsense/Interface/Autoconf.php#L41

So if in your case there is no delegated prefix with a file like "/tmp/igc1_prefixv6" (-dont know the exact name right now, also depends on your interface name-) containing your prefix it will fall back to dead:beef so kea doesnt crash.

Please say where in your case the delegated prefix is written to.

6rd does not necessarily provide a DHCPv6-delegated prefix. The available prefix may instead be derived from the 6rd configuration and the WAN IPv4 address.
Can you show your 6rd configuration and where OPNsense exposes the resulting IPv6 prefix? We currently consume the prefix made available through the normal interface prefix file mechanism.
#2
26.7, 26.10 Series / 6rd + Kea DHCPv6-PD with dynam...
Last post by HiTekRedNek - Today at 03:07:29 AM
My ISP only provides IPv6 via 6rd. I was attempting to use Identity Association plus Kea's IPv6 to pass a dynamic /60 PD to my core switch.

The problem is that my WAN interface doesn't have an IPv6 address or prefix. That's the wan_stf interface. But the code doesn't seem to look there for dynamic prefix option in Kea -> DHCPv6

It just passes "dead:beef:x:x:x" as the prefix, never the actual prefix given to me via 6rd.
#3
26.7, 26.10 Series / Dynamic IPv6 Routing for Matte...
Last post by userunkn4wn - Today at 01:22:52 AM
Hi OPNsense Community,

I'm currently trying to figure out how to reach my Matter devices, which are on a different subnet from my Home Assistant instance.

I managed to get it working by enabling the mDNS reflector, using my Matter Border Router (IKEA DIRIGERA) as a gateway into the IoT network, and adding a static route for the Matter network's ULA prefix via this gateway.

While this setup works, it's somewhat fragile because the route is configured statically. The Matter network's ULA prefix doesn't seem to change, so that's not an issue. However, my IKEA DIRIGERA's IPv6 link-local address changes after every reboot, meaning the gateway address changes as well.

I tried enabling Router Advertisement acceptance on the interface using:

sudo ifconfig bridge2 inet6 accept_rtadv

Unfortunately, this didn't seem to work.

Does anyone have an idea how I could move away from the static route and have OPNsense automatically learn the route instead?

Having to update the route after every reboot isn't a huge issue, especially since I only noticed this behavior after weeks of running this setup successfully, but it's certainly not ideal.

Thanks in advance for any suggestions!
#4
26.7, 26.10 Series / Re: Liveview not updating afte...
Last post by kbsense - Today at 12:31:32 AM
While booted into 26.7.9_1 I am seeing hundreds of these lines in System > Log Files > Backend

Quote2026-11-15T17:02:18-06:00   Error   configd.py    [6856c23a-e340-4afd-aeb9-8e386bd24455] Script action failed with Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1. at Traceback (most recent call last):   File "/usr/local/opnsense/service/modules/actions/script_output.py", line 94, in execute     subprocess.run(script_command, env=self.config_environment, shell=True,     ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^                    check=not self.disable_errors, stdout=output_stream, stderr=error_stream)                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.13/subprocess.py", line 578, in run     raise CalledProcessError(retcode, process.args,                              output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1.
2026-11-15T17:02:17-06:00   Error   configd.py    [8e45790b-e141-46a5-87c2-e077fe35a9e5] Script action failed with Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1. at Traceback (most recent call last):   File "/usr/local/opnsense/service/modules/actions/script_output.py", line 94, in execute     subprocess.run(script_command, env=self.config_environment, shell=True,     ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^                    check=not self.disable_errors, stdout=output_stream, stderr=error_stream)                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.13/subprocess.py", line 578, in run     raise CalledProcessError(retcode, process.args,                              output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1.
2026-11-15T17:02:16-06:00   Error   configd.py    [168a3183-0bf4-497d-ad12-24b21af15142] Script action failed with Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1. at Traceback (most recent call last):   File "/usr/local/opnsense/service/modules/actions/script_output.py", line 94, in execute     subprocess.run(script_command, env=self.config_environment, shell=True,     ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^                    check=not self.disable_errors, stdout=output_stream, stderr=error_stream)                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.13/subprocess.py", line 578, in run     raise CalledProcessError(retcode, process.args,                              output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1.
2026-11-15T17:02:15-06:00   Error   configd.py    [3cd53413-2b7a-47cf-bf93-90188de8932b] Script action failed with Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1. at Traceback (most recent call last):   File "/usr/local/opnsense/service/modules/actions/script_output.py", line 94, in execute     subprocess.run(script_command, env=self.config_environment, shell=True,     ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^                    check=not self.disable_errors, stdout=output_stream, stderr=error_stream)                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.13/subprocess.py", line 578, in run     raise CalledProcessError(retcode, process.args,                              output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1.
2026-11-15T17:02:14-06:00   Error   configd.py    [8f73efab-a802-4e87-adb3-c5414e24ca68] Script action failed with Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1. at Traceback (most recent call last):   File "/usr/local/opnsense/service/modules/actions/script_output.py", line 94, in execute     subprocess.run(script_command, env=self.config_environment, shell=True,     ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^                    check=not self.disable_errors, stdout=output_stream, stderr=error_stream)                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.13/subprocess.py", line 578, in run     raise CalledProcessError(retcode, process.args,                              output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1.

And even though the gui liveview isn't updating, I am still able to see logs updating via "opnsense-log -f filter"
#5
Virtual private networks / Re: Issue with multiple wiregu...
Last post by Unsocial_Firewall - November 15, 2026, 10:48:39 PM
Thanks a lot! Yup, everything seems to work for now, and I'll do some more testing.

QuoteSure, why not, if it is working.

Well, I barely know anything about WireGuard, so I don't know all the ramifications of changing the provided subnet from ProtonVPN from /32 to /30.


The ipv6 works now aswell but there still is no static route for 10.2.0.1... (Even though it's the monitor ip)
#6
Development and Code Review / Re: netflector available as pl...
Last post by UnicronHD - November 15, 2026, 10:44:10 PM
Quote from: vicking on November 13, 2026, 08:24:13 PMThanks for the detailed answer! The diretions are right, I have now made the changes you suggest and will report back after a while of testing. For now the Sonos app doesn't see the speakers, but I will give it a while before the changes become active.

To mention, I didnt make any specific firewall rules for it.

Edit: Aaaand bam, there are the speakers again in the app. Started to work after the change in Netflector! :D
One thing, do I also need to tick "Broadcasts"?

For now, thanks for this!

Good to hear. Leave Broadcasts off: SSDP goes to the multicast group, and changing one thing at a time tells us what fixed it. Your old setup only failed now and then, so give it a couple of days before we call it solved.

The wait right after the change may come from the firewall. With the relay, the speakers answer the app's searches directly, as new traffic from the Sonos VLAN to the phone's VLAN. If no rule on the Sonos VLAN interface passes it, those answers are dropped and the app has to wait for the speakers' own periodic announcements. Firewall > Log Files > Live View shows such drops as blocked UDP from the speakers to the phone. If you see them, add a pass rule on the Sonos VLAN interface for UDP from the speakers to the phone's network.
#7
Virtual private networks / Re: Issue with multiple wiregu...
Last post by Bob.Dig - November 15, 2026, 10:43:30 PM
Quote from: Unsocial_Firewall on November 15, 2026, 10:23:01 PMat a time sets an additional route to the gateway/DNS address.
Monitor IPs get a route added automatically.

Quote from: Unsocial_Firewall on November 15, 2026, 10:23:01 PMCan I leave them like this?
Sure, why not if it is working.

Quote from: Unsocial_Firewall on November 15, 2026, 10:23:01 PMso I should also just change this 2a07:b944::2:2/128 to /126?
Never done it myself (IPv6 VPN) but it is looking good to me.
#8
Virtual private networks / Re: Issue with multiple wiregu...
Last post by Unsocial_Firewall - November 15, 2026, 10:23:01 PM
The tunnel IP for the first instance, 10.2.0.1/32, did set the route properly until I disabled the static routes.

I changed the tunnel IP from 10.3.0.1/32 to /30 .

I'm a bit confused: the routes now look correct, and everything works when I set both the first and second instances to a /30 subnet.

For some reason, only a single WireGuard instance at a time sets an additional route to the gateway/DNS address. Right now it's 10.3.0.1; before, it was 10.2.0.1. I am not using any manual routes right now.

My routes now look like this:


10.2.0.0/30        link#14            U               wg0
10.2.0.2           link#3             UHS             lo0
10.3.0.0/30        link#15            U               wg1
10.3.0.1           link#15            UHS             wg1
10.3.0.2           link#3             UHS             lo0


Can I leave them like this?  also I have issues with an additional third ipv6 wg so I should also just change this 2a07:b944::2:2/128 to /126?
#9
26.7, 26.10 Series / Re: Liveview not updating afte...
Last post by cookiemonster - November 15, 2026, 10:05:58 PM
working fine here. Firefox 159.0.1 on MS Win 10, the client I had available now.
#10
26.7, 26.10 Series / Re: what causes this? [zone: p...
Last post by nero355 - November 15, 2026, 09:49:13 PM
Quote from: XxTriviumxX on November 15, 2026, 08:54:58 PMShould i go higher?
Restore it to the default value and have a look at your MTU settings for the connection or use MSS Clamping seems to be the way to fix it after a quick search on the internet :)

QuoteWhat is going on with my router? Any tips?
Have a look at this : https://forum.opnsense.org/index.php?topic=21207.0
And apply whatever could work for you and see if it helps...