TMS zl Management and Configuration Guide ST.1.1.100430

7-182
Virtual Private Networks
Configure an L2TP over IPsec VPN
e. For Source, specify Any Address.
If you know the public addresses of all of your remote endpoints, you
could create a named object with those addresses and specify that
object here.
f. For Destination, leave Any Address or specify the local gateway IP
address.
g. Click Apply.
h. For From, select Self.
i. For To, select the remote zone.
j. For Service, select ipsec-nat-t-udp.
k. For Source, leave Any Address or specify the local gateway IP address.
l. For Destination, specify Any Address.
If you know the public addresses of all of your remote endpoints, you
could create a named object with those addresses and specify that
object here.
m. Click Apply.
12. Click Close.
13. Click Save.
Verify Routes for the L2TP over IPsec VPN
In the Network > Routing > View Routes window, verify that your TMS zl Module
knows a route to the remote endpoints. This route can be a default route, a
static route, or a route discovered through a dynamic routing protocol. The
route’s forwarding interface must be the interface with the IP address that you
specified as the local gateway address in the IKE policy (and as the local
address in the IPsec policy). This is also the IP address that L2TP clients use
to contact the TMS zl Module. If necessary, add the route.
Also note that, whenever the TMS zl Module assigns a virtual IP address to an
L2TP client, a route to pppX is automatically added to the route table. This
route is to the virtual IP address and uses the server address that you assigned
to the tunnel as the gateway address.