Category:Incoming L2TP: Difference between revisions

Category:Incoming L2TP (view source)

Revision as of 19:23, 26 August 2019

260 bytes added , 26 August 2019

m

→‎Connection Details

AA-Andrew

autoreview, Bureaucrats, editor, Interface administrators, reviewer, Administrators

12,270

edits

Revision as of 09:11, 7 June 2016 (view source) AA-Andrew (talk \| contribs) mNo edit summary ← Older edit		Revision as of 19:23, 26 August 2019 (view source) AA-Andrew (talk \| contribs) m (→‎Connection Details) Newer edit →
(12 intermediate revisions by 2 users not shown)
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 xxx@a.1) from a different ISP will ~~then~~ give you your normal IP addresses. ~~etc~~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 on http://aa.net.uk/broadband-l2tp.html~~ #There are more reasons for doing this and further information and ordering on http://aa.net.uk/broadband-l2tp.html ==Connection Details== Endpoint: ~~For L2TP as a backup please contact sales staff, for a separate L2TP connection please order via http://aa.net.uk/broadband-l2tp.html~~ l2tp.aa.net.uk or ~~Endpoint: l2tp~~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~~, MSCHAPv2 authentication~~ ===MTU=== You may have to set a lower MTU to accommodate the host ISP, ~~possible~~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. = ~~Some~~ Notes ~~from customers~~on setting up L2TP IN to AAISP: = {{AAMenu\|img=Menu-FireBrick.svg\|link=L2TP_Client:_FireBrick\|title=L2TP from FireBrick\|text=Creating a L2TP connection from a FireBrick to AAISP)}} {{AAMenu\|img=Menu-Apple.svg\|link=L2TP_Client:_OSX\|title=L2TP from OSX\|text=Creating a L2TP connection from Apple OSX to AAISP}} {{AAMenu\|img=Menu-Windows.svg\|link=L2TP_Client:_Windows\|title=L2TP from Windows\|text=Creating a L2TP connection from Windows 7 and Windows 10 to AAISP}} {{AAMenu\|img=Menu-Linux.svg\|link=L2TP_Client:_Linux\|title=L2TP from Linux\|text=Creating a L2TP connection from Linux to AAISP using xl2tpd}} {{AAMenu\|img=Menu-Routerboard.svg\|link=L2TP_Client:_Routerboard\|title=L2TP from Routerboard\|text=Creating a L2TP connection from Routerboard to AAISP}} {{AAMenu\|img=Menu-OpenWRT.svg\|link=L2TP_Client:_OpenWRT\|title=L2TP from OpenWRT\|text=Creating a L2TP connection from OpenWRT to AAISP}}