@technolust said in Split Tunnel Traffic Failing for Web Traffic:
It could be due to the name resolution not working but I'm not 100% sure.
Do an nslookup to get sure. Or even a ping to google.com or whatever.
I renamed the vpn file with redirect-gateway def1 to the original. Checked the box and the issue happens... 1.1.1.1 comes up but dns not working... Then I brought back the redirect vpn file and unchecked the box and it works
Normally this is pushed to clients by the server and hence doesn't need to be set on the client, however, it's possible.
You can enhance the clients log level to see, what configuration changes the client does in the OS with the line:
verb 3
try to provide your pfSense IP as DNS server I have a pi-hole setup as DNS server.
Should I try that IP?
Yes.
Possibly you have to add the VPN tunnel to the Resolver ACLs This part I don't recall how to do...
This is lapsed, since the Resolver is not the DNS server.
Maybe you have to configure it on the Pi-hole properly.
If you provide public DNS servers without 'redirect gateway' you would also route them over the VPN by adding them to the "Local Networks". Do I need to do this under IPv4 Local network(s) in the Tunnel Settings?
Yes, IPv4 addresses have to be added to the "Local IPv4 Networks", IPv6 to the respective other one.
Note to use CIDR notation, e.g. for Cloudflare "1.1.1.1/32".