Back up to the L2TP Category

Difference between revisions of "Category:Incoming L2TP"

From AAISP Support Site
Jump to: navigation, search
[quality revision][quality revision]
m (Connection Details)
m (Connection Details)
 
Line 17: Line 17:
 
* Username & Password as supplied
 
* Username & Password as supplied
 
* Hostname: AAISP
 
* Hostname: AAISP
* Authentication Protocol: PAP or CHAP/MSCHAPv2, but would recommend CHAP as L2TP is not encrypted
+
* Authentication Protocol: CHAP/MSCHAPv2 or PAP, but recommend CHAP, as L2TP is not encrypted
 
* Plain L2TP without any IPsec
 
* Plain L2TP without any IPsec
  

Latest revision as of 20:23, 26 August 2019

L2TP from Customers to AAISP

There are two reasons to use L2TP to connect in to AAISP:

  1. As a backup for your existing AAISP circuit in the event of a fault.
    • Logging in over L2TP using your DSL credentials (ie xxx@a.1) from a different ISP will give you your normal IP addresses. You can use this whilst your AAISP connection is being fixed.
    • This is enabled by default and available to everyone, there are no extra charges. Usage is taken from your quota in the usual way as if you were connecting over DSL.
    • The L2TP has priority over the DSL, so you'd want to bring it up/down as and when required
  2. Connect in to AAISP over a third-party internet connection.
    • This gives you your an AAISP IPv4 address and an IPv6 block. This will then give you unfiltered internet access with public IP addresses etc.
    • There are more reasons for doing this and further information and ordering on http://aa.net.uk/broadband-l2tp.html

Connection Details

  • Endpoint:
    • l2tp.aa.net.uk
    • or l2tp6.aa.net.uk
  • Username & Password as supplied
  • Hostname: AAISP
  • Authentication Protocol: CHAP/MSCHAPv2 or PAP, but recommend CHAP, as L2TP is not encrypted
  • Plain L2TP without any IPsec

MTU

You may have to set a lower MTU to accommodate the host ISP, possibly as low as 1462 (or lower for some ISPs). In theory fragments will work to allow 1500 MTU on our service, but fragments are inefficient, and if everyone sends fragmented packets that could degrade the service.

Notes on setting up L2TP IN to AAISP:

Menu-FireBrick.svg

L2TP from FireBrick

Creating a L2TP connection from a FireBrick to AAISP)

Menu-Apple.svg

L2TP from OSX

Creating a L2TP connection from Apple OSX to AAISP

Menu-Windows.svg

L2TP from Windows

Creating a L2TP connection from Windows 7 and Windows 10 to AAISP

Menu-Linux.svg

L2TP from Linux

Creating a L2TP connection from Linux to AAISP using xl2tpd

Menu-Routerboard.svg

L2TP from Routerboard

Creating a L2TP connection from Routerboard to AAISP

Menu-OpenWRT.svg

L2TP from OpenWRT

Creating a L2TP connection from OpenWRT to AAISP

Menu-Cisco.svg

L2TP from Cisco

Creating a L2TP connection from Cisco to AAISP

Menu-router.svg

L2TP from Other Routers

Creating a L2TP connection from other routers to AAISP