30.01.2015 Views

Administrator's Guide - Kerio Software Archive

Administrator's Guide - Kerio Software Archive

Administrator's Guide - Kerio Software Archive

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Kerio</strong> VPN<br />

Routes provided automatically<br />

Unless any custom routes are defined, the following rules apply to the interchange of routing<br />

information:<br />

• default routes as well as routes to networks with default gateways are not exchanged<br />

(default gateway cannot be changed for remote VPN clients and/or for remote<br />

endpoints of a tunnel),<br />

• routes to subnets which are identical for both sides of a tunnel are not exchanged<br />

(routing of local and remote networks with identical IP ranges is not allowed).<br />

• other routes (i.e. routes to local subnets at remote ends of VPN tunnels excluding the<br />

cases described above, all other VPN and all VPN clients) are exchanged.<br />

Note: As implied from the description provided above, if two VPN tunnels are created,<br />

communication between these two networks is possible. The traffic rules can be configured so<br />

that connection to the local network will be disabled for both these remote networks.<br />

Update of routing tables<br />

Routing information is exchanged:<br />

• when a VPN tunnel is connected or when a VPN client is connected to the server,<br />

• when information in a routing table at any side of the tunnel (or at the VPN server) is<br />

changed,<br />

• periodically, every 10 minutes. The timeout starts upon each update (regardless of<br />

the update reason).<br />

23.5 Example of <strong>Kerio</strong> VPN configuration: company with a filial office<br />

This chapter provides a detailed exemplary description on how to create an encrypted tunnel<br />

connecting two private networks using the <strong>Kerio</strong> VPN.<br />

This example can be easily customized. The method described can be used in cases where no<br />

redundant routes arise by creating VPN tunnels (i.e. multiple routes between individual private<br />

networks). Configuration of VPN with redundant routes (typically in case of a company with<br />

two or more filials) is described in chapter 23.6.<br />

This example describes a more complicated pattern of VPN with access restrictions for<br />

individual local networks and VPN clients. An example of basic VPN configuration is provided<br />

in the <strong>Kerio</strong> Control — Step By Step Configuration document.<br />

322

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!