Messages

Thanks a lot for your detailed explanation, apalrd!

I've now used the OPNsense Tayga plugin with 'udp-cksum-mode fwd' for about a week and didn't notice any side effects. Before creating a pull request, it would be great if we could get a few more testers. @bestboy, it would be particularly interesting if this fixes VoWiFi for you.

Code Select Expand

opnsense-patch -c plugins 3be934f
You have to re-apply the Tayga config (Services: Tayga: Apply) or reboot OPNsense after applying the patch. Restarting Tayga isn't sufficient.

Cheers
Maurice

I was having issues reliably getting wifi calling to establish a connection on all my mobile devices and after applying this patch I can reliably establish a connection.

Thank you.

I did try your suggestions but they did not clear the size of blocklist statistic in the reporting. The blocklist function itself is off. Just wanted to clear the number from appearing in the report section since it's misleading.

Maybe it's just a bug or maybe there's an alternate way of resetting the counter that I'm not thinking of.

Thanks for your help!

I was using blocklists via unbound in OPNsense but I've decided to no longer use any blocklists. The Unbound DNS reporting still shows a blocklist loaded, however I have disabled the feature altogether.

Is there a way to clear the blocklist counter in the reporting area for Unbound DNS? I can see nothing is being blocked, the dashboard is just showing an incorrect blocklist size, it should be zero.

I have searched these forums and Reddit and wasn't able to find anything on the topic.

I am on 23.1.5_4

Thanks,

I am certain I have figured this out.

So just in case anyone else comes across this warning, it means there is an interface that is pulling a delegated IPv6 address to a physical port (LAN, OPT1, etc.) but there is no link or cable plugged in.

The fix, obviously, would be to plug in your device or deactivate the interface. Otherwise the warnings will persist.

I am on this version of OPNsense:

Versions   OPNsense 22.7.8-amd64
FreeBSD 13.1-RELEASE-p3
OpenSSL 1.1.1s 1 Nov 2022

I have IPv6 through ISP natively (Verizon Fios) with the following settings:

FIREWALL: SETTINGS: ADVANCED
Allow IPv6 [checked]

INTERFACES: [WAN]

Generic configuration:
IPv6 Configuration Type [DHCPv6]

DHCPv6 client configuration:
Request only an IPv6 prefix [check]
Prefix delegation size [56]
Send IPv6 prefix hint [check]
Use IPv4 connectivity [unchecked]
Use VLAN priority [disabled]

INTERFACES: [LAN]

Generic configuration
IPv6 Configuration Type [Track Interface]

Track IPv6 Interface
Track IPv6 Interface [WAN]
IPv6 Prefix ID [ 0 ]
Manual configuration [unchecked]

I can see the firewall rules automatically added for IPv6 RFC4890 requirements (ICMP) in FIREWALL: RULES: FLOATING and
allow dhcpv6 client in WAN in FIREWALL: RULES: WAN

The warnings are as follows in SYSTEM: ROUTES: LOG FILE

2022-11-25T02:17:47-05:00   Warning   radvd   sendmsg: Network is down   
2022-11-25T02:13:09-05:00   Warning   radvd   sendmsg: Network is down   
2022-11-25T02:11:47-05:00   Warning   radvd   sendmsg: Network is down   
2022-11-25T02:06:14-05:00   Warning   radvd   sendmsg: Network is down   
2022-11-25T02:02:04-05:00   Warning   radvd   sendmsg: Network is down   
2022-11-25T01:59:45-05:00   Warning   radvd   sendmsg: Network is down   
2022-11-25T01:57:01-05:00   Warning   radvd   sendmsg: Network is down   
2022-11-25T01:53:26-05:00   Warning   radvd   sendmsg: Network is down

Despite all of the warnings, I am receiving an IPv6 IP on LAN and all VLAN interfaces, which I also have set to track with different Prefix ID's

I can also ping on all interfaces using IPv6 and Traceroute to IPv6 sites on all interfaces.

I tried to continue a similar thread but it appeared locked and it was unsolved as of this post.

I am not too concerned with the warnings since otherwise everything is working, just curious about them more so.

Thanks,