INN-RADIUS.CONF(5)

💅 inn-radius.conf — the RADIUS config glow-up (inn-radius.conf(5))

okay bestie, so this is the InterNetNews Documentation page for inn-radius.conf, and it's literally the whole entire format + attribute situation for the config file that the nnrpd RADIUS authenticator reads. if you wanna know more about the actual authenticator program itself, go peek at radius(8) 🫶

the default home for this file is inn-radius.conf in pathetc. periodt.

---

✨ DESCRIPTION ✨

so here's the vibe check on the file format, bestie:

• Blank lines? ignored. slay.
• lines starting with #? also ignored 💅
• anything after a # on a line? yeah that's ignored too, no cap.
• every other line should start with a parameter name, then a colon, then the value of that key.

except — and this is the main character detail — each section of config for a particular server gets wrapped up all cozy like this:

server <name> {
    # parameters...
}

where <name> is just some convenient label you picked for that server. it's giving name tag at a party 🎀

---

🌸 SERVER GROUP PARAMETERS 🌸

here's the full roster of available parameters, no skips, no cuts:

• radhost — the hostname of the RADIUS server you're using for auth. this parameter must be set — like, non-negotiable, bestie.
• radport — the port you query on the RADIUS server. defaults to 1645 if you don't set it.
• lochost — the hostname or IP address making the request. the RADIUS server wants an IP address, so a hostname gets translated into one with gethostbyname(). if you don't give it, this info just isn't included in the request at all (and tbh not every RADIUS setup even requires it 🙈).
• locport — the port the client being authenticated is connecting to. if you don't give it, it defaults to 119. you don't need to set this unless your readers are connecting to a non-standard port.
• secret — the shared secret with the RADIUS server. ⚠️ if your secret has spaces, tabs, or # in it, wrap it in double quotes, fr fr. this parameter must be set too.
• prefix — prepends this value onto all usernames before they get passed to the RADIUS server. super useful for sticking something like "news-" in front of every username so news users live in a whole different namespace from other accounts on the same server, iykyk. if it's not set, nothing gets prepended.
• suffix — appends this value onto all usernames before they go to the RADIUS server. usually something like "@example.com", depending on how your RADIUS server is set up. if it's not set, nothing gets appended.
• ignore-source — can be "true", "yes", "on", "false", "no" or "off". here's the tea: if it's set to false, the RADIUS authenticator checks that the response it got back came from the same IP address it sent the request to (a lil extra security, we love that). if it's set to true, it skips that verification check entirely — which is honestly normal if your RADIUS server has multiple IP addresses or if other odd things are going on and the response legit comes from a different IP 🦋

---

💖 EXAMPLE 💖

okay so picture this: a news server named news.example.com, authenticating users against radius.example.com, and appending "@example.com" to every client-supplied username before passing them to the RADIUS server. the config ate, honestly:

server example {
    radhost: radius.example.com
    lochost: news.example.com
    secret: IamARADIUSsecRET
    suffix: @example.com
}

and just to be so clear: the shared secret with the RADIUS server is "IamARADIUSsecRET" 🔥

---

🧚 HISTORY 🧚

this documentation was written by Russ Allbery <eagle@eyrie.org>, based on the comments in the sample inn-radius.conf file by Yury B. Razbegin. iconic collaboration behavior 🌈

---

👑 SEE ALSO 👑

• radius(8) — go read it, bestie, it's the whole point 💜

---

and that's the whole page!! this lil gem is from INN 2.7.4, dated 2024-05-19 — mwah, sending you the biggest kiss, go configure your RADIUS server with confidence 🎀✨🫶💅