ql2tpd(8)

πŸ“¦
version 0.1.8 Β· 2 versions
  • 0.1.8 Β· debian trixie, fedora 43, fedora 44, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 0.1.7 Β· ubuntu noble
, in debian trixie, fedora 43, fedora 44, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– ql2tpd β€” the girlies' guide to static L2TPv3 tunnels πŸ’–

okay so bestie, listen. this is a page from section 8 of the manual (ql2tpd(8)), and it's all about ql2tpd, a daemon from the go-l2tp crew. it makes static (or "quiescent") L2TPv3 tunnels and sessions, and honestly? it's giving main character energy in the data plane. let's get into it πŸ¦‹


✨ NAME ✨

ql2tpd β€” a daemon for creating static (or quiescent) L2TPv3 tunnels and sessions πŸŽ€


✨ SYNOPSIS ✨

ql2tpd [ arguments ]

like, you just run it with some arguments. that's the whole vibe.


🌸 DESCRIPTION 🌸

okay so ql2tpd is a daemon for creating static L2TPv3 (RFC 3931) tunnels and sessions. RFC 3931, noted, iconic, no cap.

Static (or quiescent) tunnels and sessions implement only the data plane transport: the L2TP control protocol is not used. literally not even invited to the party. this can be useful for setting up static L2TPv3 links where host configuration is known in advance. iykyk πŸ’…

When configured to bring up static tunnel and session instances, ql2tpd represents a more convenient way to bring up static sessions than ip l2tp commands. yes, it's the upgrade. the glow-up. periodt.

Additionally, ql2tpd supports the use of a periodic keep-alive packet for tunnels it is managing (controlled by the configuration file hello_timeout parameter). a lil "hey bestie, you still there?" packet 🫢

This allows for the detection of tunnel failure, which will then tear down the sessions running in that tunnel. so if the tunnel ghosts you, the sessions get ghosted too. it's giving consequences.

⚠️ This mode of operation must only be enabled if the peer is also running ql2tpd. like, don't send keep-alives into the void, bestie. both sides need to be in on it.

ql2tpd requires root permissions to run πŸ‘‘ (yes, actual root, we're not kidding), and is driven by a configuration file which details the tunnel and session instances to create.

For further details of the configuration format, please refer to ql2tpd.toml(5). go read it, it's short, i promise πŸ“


✨ OPTIONS ✨

  • -config string β€” specify configuration file path (default "/etc/ql2tpd/ql2tpd.toml") πŸŽ€ like if you wanna put your config somewhere else, this is the girl that tells ql2tpd where it lives
  • -verbose β€” toggle verbose log output πŸ”₯ turn it on and suddenly you know everything that's happening. very nosy, very useful

πŸ’œ SEE ALSO πŸ’œ


πŸ‘‘ AUTHORS πŸ‘‘

Katalix Systems, Ltd.


and that's the whole page, bestie! 🌈 this was ql2tpd(8) from go-l2tp v0.1.8, dated May 2024 β€” so yeah, fresh-ish, cute, done. go build some tunnels, stay rooted, and don't forget your config file πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’…πŸ«Ά

πŸ“¦ where this page comes from