L2TP from Customers to AAISP
There are two reasons to use L2TP to connect in to AAISP:
- As a backup for your existing AAISP circuit in the event of a fault.
- Logging in over L2TP using your DSL credentials (ie email@example.com) 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
- 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
- or l2tp6.aa.net.uk
- Username & Password as supplied
- Hostname: AAISP
- Plain L2TP without any IPsec, MSCHAPv2 authentication
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:
Creating a L2TP connection from a FireBrick to AAISP)
Creating a L2TP connection from Apple OSX to AAISP
Creating a L2TP connection from Windows 7 and Windows 10 to AAISP
Creating a L2TP connection from Linux to AAISP using xl2tpd
Creating a L2TP connection from Routerboard to AAISP
Creating a L2TP connection from OpenWRT to AAISP
Creating a L2TP connection from Cisco to AAISP
Creating a L2TP connection from other routers to AAISP
Pages in category "Incoming L2TP"
The following 13 pages are in this category, out of 13 total.