autoreview, editor
94
edits
L2TP Client: Debian: Difference between revisions
m
removed pointless swearing
m (→Preparation) |
m (removed pointless swearing) |
||
| (7 intermediate revisions by 2 users not shown) | |||
|
===Introduction===
I recently moved [https://libreboot.org/ libreboot.org] hosting to a much faster network than what it had before, but the new ISP doesn't assign static IPv4 or IPv6 subnets on the line, and it has all kinds of restrictions, though speed, uptime and latency are all excellent. I decided therefore to set up a tunnel connection using a&a's [https://www.aa.net.uk/broadband/l2tp-service/ L2TP tunnel service]. It's just like a regular VPN service, but specifically intended for people like me who need fixed IPs to host servers on. It's really very good, and my old hosting was done via one of their handline (VDSL) connections, but I decided I needed something faster via their L2TP service instead.
I was toying with OpenBSD as a router but decided to shelve that project for a while, and go with something I'm very familiar with - Debian Linux!
You could also just use pfsense but I really just like running a router on Debian on an old ThinkPad for some reason. pfsense is "too much gun", for my purposes. Again, I just like Debian for no reason, for this specific purpose.
Adapt this guide according to your distro. Basically all we want to do is do PPP via L2TP and enable packet forwarding in Linux, so that packets can pass between two interfaces. We will have these interfaces:
* WAN port (ethernet) - upstream ISP
* LAN port (ethernet) - packets ONLY routed between it and the tunnel, NOT the WAN port directly
In other words, this will be a completely enclosed network. The setup that I'm describing here is for a standalone L2TP service, not the failover setup that a&a also provides on their hardlines.
This guide assumes that you already have some dumb cable router or something like that set up, with DHCP. Your L2TP router will sit behind that, using either a static IP or DHCP, whatever you want, doesn't matter, that's just to get you on the internet so we can set up L2TP and route IPs through that.
This setup also assumes that you have an IPv4 subnet e.g. /29 or /28 from a&a. I happened to have a /28 in my setup, because I was such a sport and a&a decided to give that to me on my L2TP, since I had one on my old VDSL line but later switched to virgin for greater speed, to use A&A L2TP with. Openreach PON fibre isn't available in my area when I made this guide.
==Preparation==
===Interface names===
In my case, I had these physical interfaces:
*
*
Yours may differ, so adapt accordingly.
===Firewall===
I will not configure a firewall on this network. I always get an IPv4 subnet from a&a either on hardlines or L2TP, and I run an open network. The router is always hardened to only allow local connections, for security.
No NAT/DHCP either. If local hosts want to firewall themselves, they can.
If I want NAT/DHCP inside such a network, I usually plug in an OpenWRT router and set a static IP on the WAN port for that.
Essentially, I like my main network to be "invisible". Just plug in and set an IP (from the public subnet) and you're good to go. This assumes you have good physical security and/or you trust the people that have access to it.
You should not connect anything insecure directly to this main network. For example, your playstation or proprietary Windows PC or something like that, should be heavily firewalled behind e.g. OpenWRT router.
This type of network is useful to me because I run lots of servers via a&a, so I need great flexibility. This is just a very simple setup that *works*.
===Traffic shaping / QoS===
You might configure <tt>codel</tt> which is nice for QoS but that's beyond the scope of this article.
===Debian packages to install===
apt-get install ppp pppoe xl2tpd iproute2 tcpdump net-tools resolvconf
You may also want
You should install these packages BEFORE doing anything else. Just connect via DHCP or something and install these. You could also grab them from Debian installation media.
===Network configuration===
In the network configuration below, my normal router was a thinkpad connected to wifi, sharing that over ethernet. It was just a test setup. On that DHCP server on the thinkpad, the subnet was <tt>10.42.0.0/24</tt>, but normally you might use e.g. <tt>192.168.0.0/24</tt>.
You MUST NOT use DHCP on this connection. You have to set a static IP, so that you can set a custom route, going to <tt>90.155.53.19</tt> *via* what would otherwise be the <tt>gateway</tt> line; in this case I'd normally set <tt>gateway 10.42.0.1</tt> in the example below, but instead i set <tt>up /sbin/ip route add 90.155.53.19/32 via 10.42.0.1 dev enp14s0</tt>. This makes all traffic on IPv4 route through the L2TP instead of directly through the main upstream, in this case virgin media.
'''And do the same for any other IP addresses that l2tp.aa.net.uk resolves to. Note that IPs may be added with or without warning.'''
The fact that I used Virgin Media on this line is irrelevant. You can use L2TP on any ISP. Adapt the config below to your needs, accordingly:
===/etc/network/interfaces===
<syntaxhighlight lang=bash>
source /etc/network/interfaces.d/*
# NOTE: no hardline so PPP not configured here. This is handled via xl2tpd
</syntaxhighlight>
NOTE: We shall re-edit this file later. For now though, our purpose is only to get online.
NOTE: IP address
===Enabling IP forwarding===
To tell our Linux router to actually forward traffic, you must first enable IP forwarding in <tt>/etc/sysctl.conf</tt>.
===/etc/sysctl.conf===
#net.ipv4.ip_forward=1
And this line (NOTE: disables stateless address autoconfiguration)
sysctl -p
This will reload
===L2TP===
It may seem counter-intuitive above, that we've configured PPP as though we're on a hardline, but this is important for the next step. A&A provides L2TP without authentication, but then you authenticate via PPP routed through L2TP.
Debian kernels should already have the correct modules, but otherwise you must ensure that the <tt>CONFIG_PPPOL2TP</tt> and <tt>CONFIG_L2TP</tt> options are enabled in your kernel configuration.
It should be noted that A&A L2TP service is (as of this day) currently without IPSEC or other encryption such as wireguard. This is less than ideal, but you will likely be doing a lot of encrypted things online anyway (lots of websites are https-aware nowadays).
You will not be able to use DNS until the L2TP is up, so we will use A&A's IP address for <tt>l2tp.aa.net.uk</tt>, which is <tt>90.155.53.19</tt>.
===/etc/xl2tpd/xl2tpd.conf===
Place the following contents:
<syntaxhighlight lang=bash>
[lac aaisp]
lns = 90.155.53.19
require authentication = no
pppoptfile = /etc/ppp/options.aaisp
</syntaxhighlight>
===/etc/ppp/options.aaisp===
Create this file, and place the following contents:
NOTE: the
<syntaxhighlight lang=bash>
+ipv6
ipv6cp-use-ipaddr
noauth
ifname ppp-aaisp-l2tp
</syntaxhighlight>
===PPP IF Up/Down scripts===
PPPoE and L2TP are managed by <tt>pppd</tt>, which executes if up/down scripts when interfaces go up or down. We shall manipulate this accordingly:
===/etc/ppp/ipv6-up.d/0000-defaultroute===
This file sets a default route on IPv6, but it can be (ab)used in general to handle L2TP/PPP going up/down. This file is for when the link goes *up*.
A default route must be set!
We already created this file earlier, and now we shall modify it:
<syntaxhighlight lang=bash>
#!/bin/bash
/bin/logger $1 is up
# ip route add default dev ppp-aaisp-l2tp proto static scope link metric 50 # hack, got my IPv6 working on host behind the LAN
fi
</syntaxhighlight>
Don't forget:
===/etc/ppp/ipv6-down.d/0000-defaultroute===
The routes must be deleted, when the line goes down:
<syntaxhighlight lang=bash>
#!/bin/bash
/bin/logger $1 is down
# system startup that does the same, should ensure maximum uptime
fi
</syntaxhighlight>
Don't forget:
===xl2tpd control file===
Create the xl2tpd control file:
echo "c aaisp" > /var/run/xl2tpd/l2tp-control
A&A prioritises routing down L2TP, but since this is standalone, you shouldn't need to worry much. However, we shall configure routing next, just to be sure.
NOTE: The above is basically how you turn on or off your L2TP internetz. You can echo 'd aaisp' to the control file to turn it off.
You need to decide whether you want L2TP turning on or off in your router. In some situations, it may not actually be desirable for it to autostart, like if you just want to quickly test a new network but aren't ready for it to go in production yet.
We cover the control file last, because we need everything else covered to already be in place in order for everything to Just Work.
Assuming that the above works, this should create a network interfaced named <tt>ppp-aaisp-l2tp</tt>, which is PPP via L2TP.
===Notes about IP routing===
My A&A IPs are:
My desired setup is:
* router LAN port is eno0 and has an IPv4 and v6 address, the v4 one is from the assigned /28 as above
* router LAN port set with IPv4 address of 81.187.172.129
* hosts behind the LAN port, via a switch, can set another IPv4 addresses e.g. 81.187.172.130, using 81.187.172.129 as gateway
* NOTE: I don't need DHCP/NAT etc on the main router because /28 IPv4. If I need NAT, I just plug in an openwrt router and set a static IP on its WAN slot, from the /28
IPv4:
===Other configurations===
The
===Auto-connect===
Due to the way xl2tpd works (control files), I concluded that the best way to handle this is with crontab. As root, do:
crontab -e
In there, insert:
* * * * * echo "c aaisp" > /var/run/xl2tpd/l2tp-control
You might also add something like this, for resolving domain names:
* * * * * echo "nameserver 217.169.20.20" > /etc/resolv.conf
This L2TP routing setup is a bit hacky, and this guide could use some refinement.
The <tt>@reboot</tt> line is probably redundant, since this will just run every minute anyway. I really wouldn't worry about it.
The last line that says "reboot" will run at boot time, for each and every boot. It will also run again, once every minute. If the L2TP is online, running the command is harmless and will simply exit.
==Security==
You should configure SSH to accept keys only and (optional) only listen on a local IP address (e.g. 10 network). This is beyond the scope of the article, but it's quite trivial to set up.
or configure for ssh key authentication with no password fallback.
ListenAddress 10.0.0.42
You can find useful logs in
==Testing==
The following commands may be useful later, to debug issues:
ip route
| |||