Smokeping_probes_Radius(3)

💖 NAME 💖

hiii bestie 🫶 welcome to Smokeping_probes_Radius(3) — aka Smokeping::probes::Radius, the RADIUS authentication probe for SmokePing. this is literally the glow-up version of the manpage, and no cap, every fact is still here 💅✨

🌈 OVERVIEW 🌈

this probe measures RADIUS authentication latency for SmokePing. that’s the vibe check: how long is RADIUS auth taking? ⏱️💖

✨ SYNOPSIS ✨

 *** Probes ***

 +Radius

 forks = 5
 offset = 50%
 passwordfile = /some/place/secret
 secretfile = /another/place/secret
 step = 300

 # The following variables can be overridden in each target section
 /^influx_.+/ = influx_location = In the basement
 allowreject = true
 mininterval = 1
 nas_ip_address = 10.1.2.3
 password = test-password
 pings = 5
 port = 1645
 secret = test-secret
 timeout = 5
 username = test-user # mandatory

 # [...]

 *** Targets ***

 probe = Radius # if this should be the default probe

 # [...]

 + mytarget
 # probe = Radius # if the default probe is something else
 host = my.host
 /^influx_.+/ = influx_location = In the basement
 allowreject = true
 mininterval = 1
 nas_ip_address = 10.1.2.3
 password = test-password
 pings = 5
 port = 1645
 secret = test-secret
 timeout = 5
 username = test-user # mandatory

💜 DESCRIPTION 💜

this probe measures RADIUS (RFC 2865) authentication latency for SmokePing. it’s giving “how fast can the auth handshake go” energy, periodt. 🦋

the username to be tested is specified in either the probe-specific or the target-specific variable username, and the target-specific one overrides the probe-specific one. target section has main character energy, iykyk 👑

the password can be specified either — in order of precedence, with the latter overriding the former — in the probe-specific variable password, in an external file, or in the target-specific variable password. the location of this file is given in the probe-specific variable passwordfile. see Smokeping::probes::passwordchecker(3pm) for the format of this file. summary: colon-separated triplets of the form <host>:<username>:<password> 🍓

the RADIUS protocol requires a shared secret between the server and the client. this secret can be specified either — in order of precedence, with the latter overriding the former — in the probe-specific variable secret, in an external file, or in the target-specific variable secret. this external file is located by the probe-specific variable secretfile, and it should contain whitespace-separated pairs of the form <host> <secret>. comments and blank lines are OK. 🙈💖

if the optional probe-specific variable nas_ip_address is specified, its value is inserted into the authentication requests as the NAS-IP-Address RADIUS attribute. cute. iconic. sometimes needed, sometimes not 😌

the probe tries to be nice to the server and does not send authentication requests more frequently than once every X seconds, where X is the value of the target-specific min_interval variable (1 by default). polite queen behavior 💅✨

🎀 VARIABLES 🎀

🌸 Supported probe-specific variables 🌸

• forks — run this many concurrent processes at maximum. Example value: 5. Default value: 5. 🧚
• offset — if you run many probes concurrently you may want to prevent them from hitting your network all at the same time. using the probe-specific offset parameter you can change the point in time when each probe will be run. offset is specified in % of total interval, or alternatively as random, and the offset from the General section is used if nothing is specified here. note that this does NOT influence the rrds itself, it is just a matter of when data acquisition is initiated. (this variable is only applicable if the variable concurrentprobes is set in the General section.) Example value: 50%. ⏰
• passwordfile — location of the file containing usernames and passwords. Example value: /some/place/secret. 🍓
• secretfile — a file containing the RADIUS shared secrets for the targets. it should contain whitespace-separated pairs of the form <host> <secret>. comments and blank lines are OK. Example value: /another/place/secret. 🙈
• step — duration of the base interval that this probe should use, if different from the one specified in the Database section. note that the step in the RRD files is fixed when they are originally generated, and if you change the step parameter afterwards, you’ll have to delete the old RRD files or somehow convert them. (this variable is only applicable if the variable concurrentprobes is set in the General section.) Example value: 300. 💀

🦋 Supported target-specific variables 🦋

• /^influx_.+/ — this is a tag that will be sent to influxdb and has no impact on the probe measurement. the tag name will be sent without the influx_ prefix, which will be replaced with tag_ instead. tags can be used for filtering. Example value: influx_location = In the basement. 🏠
• allowreject — treat "reject" responses as OK. Example value: true. ✅
• mininterval — the minimum interval between each authentication request sent, in (possibly fractional) seconds. Default value: 1. ⏳
• nas_ip_address — the NAS-IP-Address RADIUS attribute for the authentication requests. not needed everywhere. Example value: 10.1.2.3. 📍
• password — the password for the user, if not present in the password file. Example value: test-password. 🔐
• pings — how many pings should be sent to each target, if different from the global value specified in the Database section. note that the number of pings in the RRD files is fixed when they are originally generated, and if you change this parameter afterwards, you’ll have to delete the old RRD files or somehow convert them. Example value: 5. 📡
• port — the RADIUS port to be used. Example value: 1645. 🔌
• secret — the RADIUS shared secret for the target, if not present in the secrets file. Example value: test-secret. 🤫
• timeout — timeout in seconds for the RADIUS queries. Default value: 5. ⏱️
• username — the username to be tested. Example value: test-user. this setting is mandatory. 😭👑

bestie, do not skip username — it’s mandatory fr fr 💅

👑 AUTHORS 👑

Niko Tyni <ntyni@iki.fi> wrote this. shoutout to the icon who made it happen 💜✨

💀 BUGS 💀

there should be a more general way of specifying RADIUS attributes. noted, bestie 🫶

---

okay that’s the whole page, bestie — from SmokePing 2.9.0, dated 2025-06-30 💖🫶✨