Ok, fixed it. Stupid error / typo on IP address... Thanks for the assist @franco!
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: franco on December 05, 2025, 02:29:11 PMTry the plugin at 1.8 via 25.7.9.
Quote from: Patrick M. Hausen on August 01, 2025, 10:30:58 AMWhen you cloned the original rules does that mean there are now two rules for the same port but two different devices? I assume on WAN inbound? That doesn't work. You can only have one destination device for each port.
Quote from: pmhausen on March 08, 2023, 01:22:36 PMQuote from: lmnsour on March 06, 2023, 06:04:39 PMSorry, no idea. I do not mess with Microsoft products talking to Microsoft, Apple products talking to Apple, etc. If I was concerned I would not be running Windows, plain and simple.
How do I go about fixing these.
Keeping systems maintained and up to date is far more important from a security standpoint.
Kind regards
Patrick
Quote from: pmhausen on March 06, 2023, 08:47:18 AMAhh, yeah I figured.
You will need to refresh the client's DHCP lease, so it picks up the new DNS settings. Also check your DHCP configuration for explicitly specified DNS servers. If you disable Unbound, it cannot serve clients.
Quote from: lmnsour on March 05, 2023, 08:24:54 PM
I disabled Unbound DNS and reconfigured OPNSENSE settings for the DNS server and nothing worked. Had to re-enable Unbound DNS to get connection back.