Messages

Just FYI:  found that ZenArmor is blocking npr.org as a warez site.  The npr.org site is actually a news site belonging to National Public Radio.

Windows 11 22h2 is the SMB host, Windows 10 22h2 is the SMB client.

Running ZenArmor engine 1.14.2, database 1.14.23072611.

SMB connection fails unless ZenArmor is configured in Passive mode.

What is the setting that would allow SMB connections with ZenArmor in Routed Mode please?

I don't know if what I want to do is possible -- having setup NordVPN using OpenVPN, is there a way that a specific set of URL's can bypass the VPN?

I know you can set specific device(s) to not use the VPN, but what I want is to be able to define URL's that will not route through the VPN for all connected devices.

Any thoughts / help greatly appreciated!

Having same issue since this morning's update.

You are using Unbound in "query forwarding mode."  Basically, you are just pointing the router to NordVPN's DNS servers.

I have found a work-around, though I don't quite follow why it works.

After a cable modem reboot / restart, and I log into the firewall, dhcpd6 will be dead.  If I restart dhcpd6 and try to release / reload on the WAN interface, dhcpd6 just dies again.

However, if I start hdcpd6 and then restart the unbound DNS service, I can do a release / reload without dhcpd6 dying, restoring ipv6 connectivity.

I appreciate the tip!  Unfortunately, did not make any difference in my case.  Exact same symptoms.

OPNSense 23.1, ipv6 works but if the cable modem reboots, dhcpd6 dies.  You can restart it but ipv6 connectivity never returns. If you try to release / reload on the WAN interface, dhcpd6 immediately dies again.

To restore ipv6 connectivity, you have to reboot the firewall.

In the previous OPNSense version, same configuration, dhcp6 would stay up past a modem reboot and release / reload worked without killing the service.

Update -- this seems to relate to issues with Unbound DNS.  Because of not being able to check email (Comcast), I have moved back from Unbound to using a separate Pi.Hole DNS server, and this appears to resolve the issue with the telemetry gadget not showing correctly.

With 23.1, on the Dashboard, the widget for Telemetry Status for ET Telemetry just shows a spinning circle.  The first time I noticed, I removed the widget and added it back, which seemed to resolve it.  However, a few minutes later, back to the spinning circle.

Thanks.