Category:L2TP Handover: Difference between revisions
m (AA-Andrew moved page Category:Mobile L2TP Handover to Category:L2TP Handover) |
mNo edit summary |
||
(20 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
<indicator name="Front">[[File:Menu-datasim.svg|link=:Category: |
<indicator name="Front">[[File:Menu-datasim.svg|link=:Category:Data SIMs|30px|Back up to the Data SIM Category Page]]</indicator><indicator name="L2TP">[[File:Menu-L2TP.svg|link=:Category:L2TP|30px|Back up to the L2TP Category]]</indicator> |
||
= Overview = |
= Mobile and DSL L2TP Handover: Overview = |
||
Our data SIMs allow for the possibility of L2TP hand over |
Our "data-only" SIMs allow for the possibility of L2TP hand over to your own LNS. (Note: our SIP2SIM SIMs don't have this ability - sorry) |
||
Less common, but still possible, is relaying a DSL circuit to your own LNS, eg, an ADSL, VDSL, FTTP etc circuit. |
|||
⚫ | |||
This means that the data SIM (or DSL line) connects directly in to your network, and you control the IP address allocation, routing and any fire-walling or filtering as you wish. |
|||
The settings for a SIM can be set on the control pages. For DSL connections the L2TP settings are set by staff, so please do contact them for any changes or setup. The information that would be requested is: |
|||
*Target IP (with an optional backup IP) - the L2TP server at your side |
|||
*Host - the hostname we present |
|||
*Secret - the password we use (optional) |
|||
⚫ | |||
{{CPbox|#Click on the SIM ICCID you want to edit |
{{CPbox|#Click on the SIM ICCID you want to edit |
||
Line 12: | Line 21: | ||
[[File:Clueless-SIM-l2tp.png|none|frame|L2TP relay settings on the Control Pages]] |
[[File:Clueless-SIM-l2tp.png|none|frame|L2TP relay settings on the Control Pages]] |
||
==DSL Configuration== |
|||
=Information about Tunnels and Credentials= |
|||
*Wholesalers will usually already have their configuration set to relay based on their realm. |
|||
*For individual circuits please contact staff to set up relaying on to your own L2TP server. |
|||
L2TP establishes a tunnel, and over that tunnel it establishes one or |
|||
more sessions, each of which uses PPP. |
|||
The tunnel requires an endpoint address (e.g. l2tp.aa.net.uk or |
|||
90.155.53.19) and a hostname (which is sort of the login name for the |
|||
tunnel). The tunnel can also include a secret, which we do not use for |
|||
our L2TP outbound service to customer's L2TP servers. |
|||
Once the tunnel is established, a session can be established over the |
|||
tunnel. The session does not have to have any authentication, but it is |
|||
normal for the endpoints to negotiate PAP or CHAP using LCP, and so the |
|||
connecting end will need a username and password to complete the PPP |
|||
level authentication. |
|||
So, in total, you would need: |
|||
#Tunnel IP |
|||
#Tunnel Hostname |
|||
#Tunnel Secret (if used) |
|||
#Session Username |
|||
#Session Password |
|||
An L2TP session is PPP and can negotiate whatever authentication it |
|||
likes for the session. In practice this is usually done by a proxy, so |
|||
in the case of both SIMs and Broadband we will receive proxied |
|||
negotiation details for the circuit, and will pass on those proxy |
|||
details to the far end. |
|||
=Technical Pages= |
|||
The far end should ideally used these details, which also include a |
|||
For more technical information, please see: |
|||
calling station ID (circuit ID or ICCID). In the case of broadband the |
|||
*[[L2TP Tunnels and Credentials|L2TP Sessions and Credentials]] |
|||
far end could restart LCP and re-run PPP authentication if it wished, |
|||
*[[Mobile L2TP Technical|Mobile L2TP Technical information]] |
|||
end to end with the connecting device. This is not usually possible with |
|||
a SIM though, so proxied credentials should be accepted. |
|||
=Device Configuration= |
|||
Note, also, for a SIM, it is possible for the connection to have no |
|||
See the pages below for example configurations of L2TP servers. |
|||
authentication, i.e. LCP has negotiated no authentication protocol. This |
|||
may upset some L2TP endpoints if they are not expecting this. They |
|||
should authenticate on the ICCID (calling station) in such cases. |
|||
=Setting up your end= |
|||
There are pages below with help in setting up equipment at your end... |
|||
[[Category: |
[[Category:Data SIMs]] |
||
[[Category:L2TP]] |
[[Category:L2TP]] |
Latest revision as of 21:00, 11 August 2019
Mobile and DSL L2TP Handover: Overview
Our "data-only" SIMs allow for the possibility of L2TP hand over to your own LNS. (Note: our SIP2SIM SIMs don't have this ability - sorry)
Less common, but still possible, is relaying a DSL circuit to your own LNS, eg, an ADSL, VDSL, FTTP etc circuit.
This means that the data SIM (or DSL line) connects directly in to your network, and you control the IP address allocation, routing and any fire-walling or filtering as you wish.
The settings for a SIM can be set on the control pages. For DSL connections the L2TP settings are set by staff, so please do contact them for any changes or setup. The information that would be requested is:
- Target IP (with an optional backup IP) - the L2TP server at your side
- Host - the hostname we present
- Secret - the password we use (optional)
SIM Configuration
Accessing This Feature
Access is via the Control Pages as follows:
- Log in to the Control Pages with your xxx@a login
- Click on the SIM ICCID you want to edit
- Fill in the L2TP relay information there
You can enter the IP address of your LNS (and an alternative if you like), and a shared secret if you want to do tunnel authentication.
DSL Configuration
- Wholesalers will usually already have their configuration set to relay based on their realm.
- For individual circuits please contact staff to set up relaying on to your own L2TP server.
Technical Pages
For more technical information, please see:
Device Configuration
See the pages below for example configurations of L2TP servers.
Pages in category 'L2TP Handover'
The following 5 pages are in this category, out of 5 total.