L2TP Client: Debian: Difference between revisions

L2TP Client: Debian (view source)

Revision as of 21:33, 12 March 2023

126 bytes added , 12 March 2023

m

removed pointless swearing

Drsox

autoreview, editor

94

edits

Revision as of 19:41, 30 November 2022 (view source) Reedy (talk \| contribs) (less fail) ← Older edit		Revision as of 21:33, 12 March 2023 (view source) Drsox (talk \| contribs) m (removed pointless swearing) Newer edit →
(One intermediate revision by one other user not shown)
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 ~~shitware~~ 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. 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: