Please , Idont want to reinstall again!!!!
-
An outbound NAT rule exactly like the one you have on WAN for localhost.
However with WANGW as the default that should be the default route. Unbound should try to use that.
-
-
-
Do you see states created by Unbound when set to localhost?
-
You should see states like:
WAN udp 172.21.16.85:6334 (127.0.0.1:13521) -> 198.41.0.4:53 MULTIPLE:SINGLE 1 / 1 56 B / 1 KiB WAN udp 172.21.16.85:20807 (127.0.0.1:4964) -> 193.0.14.129:53 MULTIPLE:SINGLE 1 / 1 60 B / 1 KiB -
-
@stephenw10 Did save resolver settings with localhost, but no any info about WAN in states only MULLVAD interface, Before set default gateway in auto in routing
-
Is it running in forwarding mode?
What DNS servers are configured if so?
If they are the Mulvard servers and have static routes over the VPN then it will always use that. That should work as long the VPN is up.
-
-
-
Check the routing table. Is there a default route? Is it valid?
-
-
-
That's not a default route. It should like:
-
Ok but you do have a /1 route via the VPN tunnel. So probably the VPN provider is pushing that route to you when it connects. That should be OK as long as Unbound has an OBN rule to allow access from localhost over the VPN.
-
-
@stephenw10 So, should be remaining on WAN outside interface for unbound?
-
-
OutBound NAT.
The /1 route being passed by the VPN provider is a more precise route than the default route which is /0. So it would be used in preference.
That's likely why you see the DNS states on the VPN interface. That should work.
I prefer to set the VPN client not to pull routes from the server and then add policy routing for clients/subnets I want to use the VPN.
-
S stephenw10 moved this topic from Problems Installing or Upgrading pfSense Software on
