While we try our best, our support options may be limited if firewalls/routers in between VPN Tracker and the VPN gateway), we cannot guarantee that a connection can be established under any circumstances. ![]() Resolving a Network Conflict using Traffic Control you change connection parameters while we're trying to debug the settingsīy default, traffic to the remote network cannot be sent through the VPN tunnel if it is using the same network as the local network.your network administrator does not cooperate.you do not provide the information we need in order to assist you (see above).you use a device which we did not test ourselves (most devices work just fine with VPN Tracker, though, and we're happy to take a look even at issues with untested VPN gateways). > Check "Force traffic over the VPN if remote networks conflict with local networks" You can use Traffic Control and VPN Tracker will send non-essential local network traffic over the VPN. Note that you will never be able to reach the following addresses over VPN: The IP address of your local router, your DHCP server, and your DNS server(s). If you need to reach those IPs over VPN, you will have to resolve the network conflict instead of using Traffic Control. Change the local network to use a different network address.You have two basic options for resolving a conflict: The same applies for any IPs that you need to reach locally and over VPN. Change the remote network to use a different network address.In most situations, this will entail changing the LAN settings on the local router (including DHCP settings if DHCP is used). With most setups, this entails changing the LAN on the VPN gateway (including DHCP settings if DHCP is used), and changing the IPs used by devices on the VPN gateway's LAN (or triggering a DHCP refresh, if DHCP is used). ![]() Finally, change the remote network in VPN Tracker to match the new settings If the LAN is used in the VPN settings (such as for policies or firewall rules), these will need to be changed as well. According to our informal statistics, conflicts are least likely using these networks: If you decide to change the remote network, it makes sense to choose a private network that less commonly used. However, since wireless network operators sometimes choose to use the entire 10.0.0.0/8 network, the first two options are preferred. If you have a more sophisticated VPN gateway, in particular a SonicWALL, you may be able to set up an alternative remote network on the VPN gateway that is mapped 1:1 through Network Address Translation (NAT) onto the actual network. Users can then connect to this network instead if they have a conflict of networks. We have a guide available that describes this approach for SonicWALL devices. If the conflict is caused by virtual network interfaces (e.g. Parallels, VMware), see here for more information. This means that it will work with almost all devices supporting these types of VPN connections.Ī list of tested devices is available in VPN Tracker and on our website: VPN Tracker supports industry standard OpenVPN, IPsec, L2TP and PPTP protocols.
0 Comments
Leave a Reply. |