L2TP Client: Debian: Difference between revisions

(3 intermediate revisions by 2 users not shown)

Line 1:

<indicator name="L2TP">[[File:Menu-L2TP.svg|link=:Category:Incoming L2TP|30px|Back up to the Incoming L2TP Category]]</indicator>

[[Category:Incoming L2TP]]

Also see this blog post by a customer using Debian and our L2TP service: https://www.ashbysoft.com/posts/debian-aaisp-l2tp/

== Standalone A&A L2TP router on Debian Linux ==

Line 45:

Line 48:

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.

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*.

Line 51:

Line 54:

===Traffic shaping / QoS===

You might configure <tt>codel</tt> which is nice for QoS but that's beyond the scope of this article.

You might configure <tt>codel</tt> or (better) <tt>cake</tt> which is nice for QoS but that's beyond the scope of this article. See: https://openwrt.org/docs/guide-user/network/traffic-shaping/sqm for some tips.

===Debian packages to install===