This thread is for @RMerlin
On my RT-AC86U running Merlin 386.7_2, I run the VPN client in exclusive DNS mode because it is necessary to use all of our streaming services.
In the VPN Director I have rules to select WAN/VPN for the home computers in our network. Local nslookup queries are successful on the computers that are set for WAN, and fail on computers set for VPN tunnel. This behavior is consistant on Linux and Windows machines. For computers set to use the router's client VPN (packet sniffing with tcpdump-->pcap file and viewing on Wireshark) the local-src to local-dest DNS requests are being passed to upstream VPN servers, which is guaranteed to fail. The upstream responds correctly having recognized a private network request, with...
I suppose that this could be classified as a bug, because passing a private network DNS request to an upstream DNS server will fail every time, and there is no need to enter the tunnel for local requests. Would it be possible to implement a fix for this behavior ? Thanks in advance.
On my RT-AC86U running Merlin 386.7_2, I run the VPN client in exclusive DNS mode because it is necessary to use all of our streaming services.
In the VPN Director I have rules to select WAN/VPN for the home computers in our network. Local nslookup queries are successful on the computers that are set for WAN, and fail on computers set for VPN tunnel. This behavior is consistant on Linux and Windows machines. For computers set to use the router's client VPN (packet sniffing with tcpdump-->pcap file and viewing on Wireshark) the local-src to local-dest DNS requests are being passed to upstream VPN servers, which is guaranteed to fail. The upstream responds correctly having recognized a private network request, with...
I suppose that this could be classified as a bug, because passing a private network DNS request to an upstream DNS server will fail every time, and there is no need to enter the tunnel for local requests. Would it be possible to implement a fix for this behavior ? Thanks in advance.