Messages

Ah sorry I missed the gateway part. You can't reach your OPNsense's LAN IP (192.168.1.1) with that rule.
Add '!This Firewall' to that rule (Destination: 'This Firewall' and turn on the 'Destination/Invert').

Already try this rule: LAN net ---> !This firewall --> WANPPPOE with the same result, no luck.

Is unbound listening on 192.168.1.1? Also verify your lan.net is allowed in unbound access list

Check as well that Query forwarding is enabled to correct servers.
Rgds

Sure things, because Unbound already works when Firewall rule uses Default gateway

Hello,

I've just installed OPNsense 23.1.7_3-amd64 and found a strange behavior I've never seen before.

I have only one WAN and set firewall rule, NAT and Unbound like normal, everything work fine.








I test to see if policy route works or not before adding more VPN connection:



And headache begins, pings still ok but can not resolve DNS:




Restart Unbound, restart OPNsense and still no luck. It only resolves DNS again when I put Gateway in Firewall rule back to Default.

Please help me, thank you and much appreciate.

Sorry, double post