Category:Incoming L2TP: Difference between revisions

Category:Incoming L2TP (view source)

Revision as of 15:13, 15 April 2020

1,310 bytes added , 15 April 2020

m

→‎L2TP from Customers to AAISP

AA-Andrew

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

12,270

edits

Revision as of 12:05, 10 May 2016 (view source) AA-Andrew (talk \| contribs) m (→‎Other Hardware) ← Older edit		Revision as of 15:13, 15 April 2020 (view source) AA-Andrew (talk \| contribs) m (→‎L2TP from Customers to AAISP) Newer edit →
(29 intermediate revisions by 3 users not shown)
__NOTOC__<indicator name="L2TP">[[File:Menu-L2TP.svg\|link=:Category:L2TP\|30px\|Back up to the L2TP Category]]</indicator> =L2TP from Customers to AAISP= This is used to connect in to AAISP over a third-party internet connection. This gives you your usual AAISP IP (4 and 6) blocks and access to the internet as if you were conencted via a normal DSL circuit. There are two reasons to use L2TP to connect in to AAISP: * Hostname: l2tp.aa.net.uk▼ #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. #Regarding IP routing, The L2TP has priority over the DSL, so you'd want to bring it up/down as and when required as the DSL won't have IPs routed to it when the L2TP is up. #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: ▲* ~~Hostname:~~ 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 * MSCHAPv2 authentication = Some Notes from customers setting up L2TP IN to AAISP: =▼ ~~== Other Hardware ==~~ ~~The TL-WR741ND router works, although it can only do NAT, but is very cheap.~~ ===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. ▲= ~~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-Linux.svg\|link=Router:Linux_-_Debian_-_With_L2TP_Fallback\|title=L2TP Faillback with Linux\|text=Creating a L2TP fallback for AAISP using pppd and 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}}