Allied Telesis L2TP Tunnel user manual

Summary of the content on the page No. 1

AlliedWare™ OS
How To | Configure Dynamic Routing Over An L2TP Tunnel
Introduction
This How To Note shows an example of using a dynamic routing protocol over an L2TP
tunnel.
Running dynamic routing protocols over a secure Internet connection can be a complex
issue, with the possibility of intermittent connections causing routing problems.
OSPF (or BGP) are more connection-oriented than RIP and therefore are more susceptible
to problems caused by intermittent loss of connection between 'neig

Summary of the content on the page No. 2

An example scenario for RIP over L2TP Related How To Notes You may also find the following How To Notes useful: How To Configure Remote L2TP Tunnels How To Configure Allied Telesis and Cisco Routers To Interoperate Over L2TP How To Notes are available from www.alliedtelesis.com/resources/literature/howto.aspx. An example scenario for RIP over L2TP Our example uses two office sites that are connected via a WAN connection over the Internet using an L2TP tunnel for security. The setup (shown bel

Summary of the content on the page No. 3

An example scenario for RIP over L2TP Network Operation There is a single static route configured to bring up the L2TP tunnel and a secure point-to- point connection (PPP0) is established over the L2TP tunnel between the 'Central' and 'Remote' office routers. This allows secure communication between the offices across the Internet. Each local office site is using OSPF as their routing protocol, as it offers some advanced routing features and is scalable and flexible. The 'local' VLAN networ

Summary of the content on the page No. 4

An example scenario for RIP over L2TP Routing Considerations A routing issue to consider in this set up is the fact that RIP is relatively slow to react to route changes as it only updates, by default, every 30 seconds. To improve the responsiveness of RIP you can alter the default timers for updating, flushing and so on. You do need to keep in mind that if you lose some packets (quite possible across a lossy Internet connection) some of your routes may flap too much. So the RIP timers need

Summary of the content on the page No. 5

Configurations Configurations Central Office Router set system name=Central_Office enable l2tp enable l2tp server=both add l2tp call="tunnel" rem="tunnel" ip=10.10.10.2 ty=virtual prec=in create vlan="vlan2" vid=2 add vlan="2" port=3,4 create ppp=0 over=tnl-tunnel set ppp=0 bap=off username="chap" password="chap" enable ip add ip int=eth0 ip=10.10.10.1 mask=255.255.255.0 add ip int=ppp0 ip=192.168.1.1 add ip int=vlan1 ip=222.222.1.1 add ip int=vlan2 ip=222.222.2.1 add ip rou=10.10.10.0 mask=255

Summary of the content on the page No. 6

Remote Office Router set system name=Remote_Office enable l2tp enable l2tp server=both add l2tp call="tunnel" rem="tunnel" ip=10.10.10.1 ty=virtual prec=out create vlan="vlan2" vid=2 add vlan="2" port=3,4 create ppp=0 over=tnl-tunnel set ppp=0 bap=off username="chap" password="chap" enable ip add ip int=ppp0 ip=192.168.1.2 add ip int=eth0 ip=10.10.10.2 mask=255.255.255.0 add ip int=vlan1 ip=200.200.1.1 add ip int=vlan2 ip=200.200.2.1 add ip rou=10.10.10.0 mask=255.255.255.0 int=eth0 next=10.10.