PPPD-RADIUS(8)
β¨ PPPD-RADIUS β¨
okay bestie, welcome to the pppd-radius page from the System Manager's Manual π
this is the whole vibe of the RADIUS authentication plugin for pppd, and yes we're doing this line by line, no skipping, no cap π«Ά
π NAME π
radius.so β the RADIUS authentication plugin for pppd(8), periodt β¨
πΈ SYNOPSIS πΈ
pppd [ options ] plugin radius.so
that's it, that's the whole summoning ritual π₯
π¦ DESCRIPTION π¦
so the RADIUS plugin for pppd lets pppd do PAP, CHAP, MS-CHAP and MS-CHAPv2 authentication against a RADIUS server instead of the usual /etc/ppp/pap-secrets and /etc/ppp/chap-secrets files. literally swapping out the whole secrets-file situation for a whole server, iconic behavior π
the RADIUS plugin is built on a library called radiusclient, which has its own configuration files (usually in /etc/radiusclient) β so go consult those files for more info on configuring the RADIUS plugin, bestie, they're the ones holding the lore π
π OPTIONS π
the RADIUS plugin introduces one additional pppd option (and then, well, keeps going π). here's everything:
radius-config-filefilename β the file filename is taken as the radiusclient configuration file. and if you don't use this option at all? then the plugin uses/etc/radiusclient/radiusclient.confas the configuration file. default behavior, she's always there for you πavpairattribute=value β adds an Attribute-Value pair to be passed on to the RADIUS server on every single request. every. one. βmap-to-ifnameβ sets the Radius NAS-Port attribute to a number equal to the interface name (Default) πmap-to-ttynameβ sets the Radius NAS-Port attribute value via the libradiusclient library π§
π USAGE π
to use the plugin, simply supply the plugin radius.so option to pppd, and edit /etc/radiusclient/radiusclient.conf appropriately. easy. slay. β¨
and here's the big one: if you use the RADIUS plugin, the normal pppd authentication schemes (login, checking the /etc/ppp/*-secrets files) are skipped. not downgraded, not partially used β skipped, fr fr π
the RADIUS server should assign an IP address to the peer using the RADIUS Framed-IP-Address attribute π«Ά
π SEE ALSO π
go read those too, iykyk π
π AUTHOR π
Dianne Skoll <dianne@skoll.ca> β thank you queen, we appreciate you πΈ
k that's the whole page bestie!! this was PPPD-RADIUS(8) from the System Manager's Manual, and if you ever need to find her again, that's exactly where she lives π bye ily, go authenticate something responsibly πβ¨
π¦ where this page comes from
- alpine 3.22: ppp-doc 2.5.2-r0 Β· BSD-3-Clause AND BSD-4-Clause AND BSD-4-Clause-Shortened AND GPL-2.0-or-later AND HPND AND LGPL-2.0-or-later AND Public-Domain AND RSA-MD
- alpine 3.23: ppp-doc 2.5.2-r1 Β· BSD-3-Clause AND BSD-4-Clause AND BSD-4-Clause-Shortened AND GPL-2.0-or-later AND HPND AND LGPL-2.0-or-later AND Public-Domain AND RSA-MD
- alpine 3.24: ppp-doc 2.5.3-r0 Β· BSD-3-Clause AND BSD-4-Clause AND BSD-4-Clause-Shortened AND GPL-2.0-or-later AND HPND AND LGPL-2.0-or-later AND Public-Domain AND RSA-MD
- arch rolling: ppp 2.5.4-1
- arch rolling: ppp 2.5.4-2 Β· GPL-2.0-or-later AND BSD-3-Clause
- arch rolling: ppp 2.5.5-1 Β· GPL-2.0-or-later AND BSD-3-Clause
- debian trixie: ppp 2.5.2-1+1
- nixos 26.05: ppp 2.5.2
- nixpkgs unstable: ppp 2.5.2
- opensuse-leap 16.0: ppp 2.5.2-160000.2.2 Β· BSD-3-Clause AND LGPL-2.1-or-later AND GPL-2.0-or-later
- opensuse-leap 16.0: ppp 2.5.2-160000.2.2 Β· BSD-3-Clause AND LGPL-2.1-or-later AND GPL-2.0-or-later
- opensuse-leap 16.0: ppp 2.5.2-160000.2.2 Β· BSD-3-Clause AND LGPL-2.1-or-later AND GPL-2.0-or-later
- opensuse-leap 16.0: ppp 2.5.2-160000.2.2 Β· BSD-3-Clause AND LGPL-2.1-or-later AND GPL-2.0-or-later
- ubuntu questing: ppp 2.5.2-1+1.1
- ubuntu resolute: ppp 2.5.2-1+1.2
- ubuntu stonking: ppp 2.5.2-1+2build1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms