Exchange of routing information
An automatic exchange of routing information (i.e. of data informing about routes to local subnets) is performed between endpoints of any VPN tunnel (or between the VPN server and a VPN client). This implies that routing tables at both sides are always up-to-date (even when any changes are performed in configuration at any side of the tunnel). No manual routing is necessary if both sides (networks) use WinRoute as their default gateways.
Note: Regarding VPN clients, routing information is sent only from the server to a corresponding client.
Exchanged routes
The following rules are applied to the exchange of routing information:
-
default routes as well as routes to networks with default gateways are not exchanged (default gateway cannot be changed for remote clients and/or for remote endpoints of a tunnel),
-
routes to subnets which are identical for both sides of a tunnel are not exchanged (routing of local and remote networks with identical IP ranges is not allowed).
-
other routes (i.e. routes to local subnets at remote ends of VPN tunnels excluding the cases described above, all other VPN and all VPN clients) are exchanged.
Note: As implied from the description provided above, if two VPN tunnels are created, communication between these two networks is possible. The traffic rules can be configured so that connection to the local network will be disabled for both these remote networks.
Update of routing tables
Routing information is exchanged:
-
when a VPN tunnel is connected or when a VPN client is connected to the server,
-
when information in a routing table at any side of the tunnel (or at the VPN server) is changed,
-
periodically, once per 30 secs (VPN tunnel) or once per 1 min (VPN server). The timeout starts upon each update (regardless of the update reason).
