Sonicwall ssl vpn client not handing out dns

The VendorвЂ™s subnet was 10.0.0.0/24 (but they also had a subnet in their network for 192.168.1.0/24, which is why this would not work, our traffic would get to them, but wouldnвЂ™t make it back out over the VPN on the way back).Let me break this down into numbers that make some sense: We decided that we would mask my clientвЂ™s internal subnet to some other range so that the internal subnet wouldnвЂ™t interfere with the subnet that the vendor had internally. Normally the IPs on either side of the tunnel are different, in this case the vendor already had a subnet in their network with the same IP address range as our internal subnet, so this wouldnвЂ™t allow us to build a tunnel between the two sides wouldnвЂ™t route the traffic to the other, both would think the traffic is local.

I had to build a site to site VPN with a vendor into a network that used the same IP scheme as one of the vendorвЂ™s subnets. I recently had an opportunity to setup something that IвЂ™ve never configured before.

Sonicwall ssl vpn client not handing out dns