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.

L2TP relay settings on the Control Pages

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.

F

FireBrick L2TP Server

L

L2TP Tunnels and Credentials

M

O

OpenL2TP

@@ Line 1: / Line 1: @@
+<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>
-This page documents my experiments setting up an LNS for my Revmobile data SIMs.
+= 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.
-For the LNS, I used openl2tp running on Linux (Debian 'squeeze'). I did some experiments with xl2tpd as well.
+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.
-=SIM Configuration=
+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:
-At the moment you need to ask RevK to set up L2TP handover on a SIM. You will need to give him the IP address of the LNS, and a shared secret if you want to do tunnel authentication. More on that later.
+*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==
-=Setting up OpenL2TP=
+{{CPbox|#Click on the SIM ICCID you want to edit
-The OpenL2TP download page [http://www.openl2tp.org/downloads here] only mentions version 1.6. This didn't compile on squeeze without building the l2tp configuration parser by hand with byacc first. If you go to the website there is actually a version 1.7 available, which compiles straight out of the tarball.
+#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.
-This is the configuration I'm using -- with my IP addresses and tunnel secret removed, naturally! If you don't want tunnel authentication, leave out the '
+[[File:Clueless-SIM-l2tp.png|none|frame|L2TP relay settings on the Control Pages]]
- peer profile create profile_name=doubtless
- peer profile modify profile_name=doubtless \
- 	tunnel_profile_name=doubtless \
- 	session_profile_name=doubtless \
- 	ppp_profile_name=doubtless \
- 	peer_ipaddr=90.155.53.8 \
- 	peer_port=1701 \
- tunnel profile create profile_name=doubtless
- tunnel profile modify profile_name=doubtless \
- 	secret=<your secret here> \	# leave out if you don't want tunnel authentication
- 	auth_mode=challenge \	# leave out if you don't want tunnel authentication
- 	src_ipaddr=<your LNS IP> \
- 	our_udp_port=1701 \
- 	peer_profile_name=doubtless \
- 	session_profile_name=doubtless \
- 	ppp_profile_name=doubtless \
- session profile create profile_name=doubtless
- session profile modify profile_name=doubtless \
- 	ppp_profile_name=doubtless \
- ppp profile create profile_name=doubtless
- ppp profile modify profile_name=doubtless \
- 	auth_pap=yes \
- 	auth_chap=yes \
- 	auth_mschapv1=no \
- 	auth_mschapv2=no \
- 	auth_eap=no \
- 	auth_none=yes \
- 	auth_peer=no \
- 	dns_ipaddr_pri=<DNS IP to give to SIM> \
- 	local_ipaddr=<IP address of LNS endpoint on PPP link> \
- 	remote_ipaddr=<IP address to give to SIM> \
- 	mtu=1280 \
- 	mru=1280 \
- 	trace_flags=1024 \
+==DSL Configuration==
-I needed the src_ipaddr line in the tunnel profile because my LNS machine has several IP addresses on the same subnet, and the one that the LNS should be using is not the primary IP. openl2tp does not record the IP address that an l2tp packet came to and use that as the source address for the reply ... adding src_ipaddr fixes that.
+*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=
-=Authentication=
+For more technical information, please see:
+*[[L2TP Tunnels and Credentials|L2TP Sessions and Credentials]]
+*[[Mobile L2TP Technical|Mobile L2TP Technical information]]
+=Device Configuration=
-Enabling tunnel authentication lets you be confident that you really are talking to doubtless and not some other LAC. Without it you are limited to just trusting the incoming IP address. What this doesn't do is authenticate the individual PPP sessions over the tunnel. doubtless supplies a CHAP username (the SIM's ICCID), challenge and response which will be verified if you enable PPP proxy authentication, however I have not worked out the secret that is being used here!
+See the pages below for example configurations of L2TP servers.
-=Musings=
+[[Category:Data SIMs]]
-Authentication with GPRS connections is a bit, well, weird. The PPP connection that pppd on your laptop establishes is not all the way through to your LNS as you might expect. It isn't even terminated in the mobile network -- it's actually terminated on the modem. What this means is that the username and password you give to pppd are verified by the modem -- which just accepts anything you supply.
+[[Category:L2TP]]
-The proxy authentication username that the LAC presents is a UK 07xxx phone number. It also presents a CHAP authentication ID, challenge and response. These are ignored unless you enable allow_ppp_proxy. I haven't yet worked out what the secret is that is being used to generate the response. It isn't the l2tp tunnel authentication secret, the proxy authentication username, the ICCID, or the password that was supplied to the modem.
-The 'calling number' and 'called number' in the incoming call request are the SIM's ICCID.
-The two devices that I've been using -- a Vodafone (Huawei) K4505 and a Nokia E51 -- both behave noticeably differently when it comes to PPP and particularly IPCP.
-=Things to do=
-* Figure out what secret is used in the PPP proxy authentication.
-* Use that (or something else) to identify individual SIMs and supply the correct IP address to each one.