Messages

Why does OPNsense use tags but not releases on Github?
https://github.com/opnsense/core/tags
https://github.com/opnsense/core/releases

Github can send alerts on new releases, but not on new tags.

Anyone know how to debug this not starting?

the error is

Code Select Expand

Notice root /usr/local/etc/rc.d/os-udpbroadcastrelay: WARNING: failed to start osudpbroadcastrelay

For reference, OPNsense 2026.7.4_1 / os-udpbroadcastrelay 1.0_6 still logs these messages, but services are actually running and work fine.

In addition, it would be really nice if the plugin would support port ranges. For example; Steam uses UDP ports 27031-27036 for LAN discovery which now results in 6 separate services on the dashboard.

After turning on HTTP/2 Support in NGINX for the OPNsense Proxy host my Dashboard is fully functioning again.
I am pretty sure I had this on before 26.7 as well but I might have turned it off in trying to get 26.7 to work.

Thanks! That seems to restore most of the functionality with NGINX as well.
On the Dashboard the CPU and Traffic Graphs remain empty though and Firewall says 'Waiting for Data'.
Firewall/Log Files/Live View works now. System/Firmware/Status as well.

Seconded. Was working fine before 26.7 but now several Web GUI pages don't load completely.
For example the firewall/live view keeps loading with the spinner and the main lobby/dashboard shows nothing apart from the menu on the left.

Same errors in the Web GUI log:

 (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.85/src/mod_openssl.c.5005) SSL: addr:192.168.0.108 ssl_err:5 ret:-1 errno:35: Resource temporarily unavailable
(192.168.0.108 is the NGINX proxy.)

Everything works fine when accessing the Web GUI directly.

Thanks for thinking along!

Network hardware is not the cause as IPv6 connectivity works fine with radvd doing AR. I did suspect my Access Point configuration (multicast/igmp) at one point, but then it turned out that wired devices were also affected.

My WAN MTU is left blank (default). It says: Calculated PPP MTU: 1492. According to the Netgear test it should be 1490. According to my ISP it should be 1500. I doubt this is the culprit either as the default setting works fine with radvd doing AR.

Both Dnsmasq and radvd broadcast the correct prefix (and both /64), the client GUAs are accordingly in both setups. I will definitely investigate the RA of both radvd and Dnsmasq in more detail. Early deprecation of prefixes sounds interesting to check as well.

For a recent fresh OPNsense installation I decided to go with Dnsmasq from scratch. My setup is a PPPoE dual stack WAN connection, getting a /48 IPv6 Prefix and IPv6 gateway works fine. The LAN Interface IPv6 is using Track Interface with the WAN interface as parent and Allow manual adjustment of DHCPv6 and RA checked.

In Dnsmasq I have configured a IPv4 DHCP range, a IPv6 DHCP range (LAN Interface / :: / LAN Constructor / ra-stateless + ra-names / default 60 Interval / default 1200 Lifetime / default 86400 Lease time) and Router Advertisements in checked in Dnsmasq/General, all according to the docs: https://docs.opnsense.org/manual/dnsmasq.html#dhcpv6-and-router-advertisements. For both IPv4 and IPv6 I have also configured a DHCP Option/Option6 with a DNS4/DNS6 server address (which is on the LAN, outside OPNsense). Services/Router Advertisements (radvd) and ISC DCHPv4+6 are all disabled.

IPv4 connectivity works fine as expected. IPv6 doesn't.

All clients get IPv6 GUAs and routing looks ok. (netstat -r -n -6). The configured DNS4/DNS6 server addresses are set and all DNS requests are received in the DNS server and are answered accordingly.

IPv6 connectivity however is very unstable. Although the numbers are good, some clients do not have IPv6 connectivity at all from the start, others have it at first but drop it later. Apps and websites fail to load content, 0/10 on test-ipv6.com and all IPv6 related showing red on ip6.biz.

As this happens on all sorts of devices (Android, iOS, Linux, MacOS, Windows11), both wired and wireless I finally narrowed it down to Dnsmasq RA.
After removing the Dnsmasq IPv6 DHCP range, turning off RA in Dnsmasq/General and enabling Services/Router Advertisements (Assisted / Advertise Default Gateway checked / default 200 min / default 600 max) all is fine again for all clients.

Before hinting at a Dnsmasq RA bug, could it relate to anything (mis)configured?

For the record:
OPNsense 25.1.8_1-amd64
FreeBSD 14.2-RELEASE-p3
Dnsmasq 2.91,1
radvd 2.20