RADZAP(1)

πŸ¦‹ radzap β€” like, the FreeRADIUS Daemon manual, section 1, bestie πŸ’…

okay so welcome to radzap, aka the little cleanup crew for your active sessions database. sit down, grab a strawberry πŸ“, and let's get into it.


✨ NAME ✨

radzap β€” remove rogue entries from the active sessions database 🧹✨


🌸 SYNOPSIS 🌸

radzap [-d raddb_directory] [-h] [-N nas_ip_address] [-P nas_port] [-u
user] [-U user] [-x] server[:port] secret

no cap, that's the whole vibe. πŸ’–


πŸŽ€ DESCRIPTION πŸŽ€

so the FreeRADIUS server can be configured to keep an active session database in a file called radutmp. commands like radwho(1) read from that database. it's giving main character energy... until it gets out of sync 😭 and then it might be holding onto rogue entries. that's literally where radzap comes in β€” it cleans this database up. periodt. πŸ’…

as of FreeRADIUS 1.1.0, radzap is a simple shell-script wrapper around radwho(1) and radclient(1). slay, honestly. ✨

the sessions get "zapped" by sending an Accounting-Request packet that contains the info the server needs to delete the session record. and bestie, listen β€” radzap sends a packet to the server instead of writing to radutmp directly, because session records may also be maintained in SQL. iykyk. 🫢


πŸ’… OPTIONS πŸ’…

  • -d raddb_directory β€” the directory that holds the RADIUS configuration files. radzap reads radiusd.conf to figure out where the radutmp file lives. πŸ“
  • -h β€” print usage help information. sometimes you just gotta ask for directions, and that's valid. πŸ™ˆ
  • -N nas_ip_address β€” zap the entries that match the given NAS IP address. 🎯
  • -P nas_port β€” zap the entries that match the given NAS port. πŸšͺ
  • -u user β€” zap the entries that match the given username (case insensitive). πŸ”
  • -U user β€” zap the entries that match the given username (case sensitive). πŸ‘‘
  • -x β€” enable debugging output. turn the lights on, we're investigating πŸ”₯
  • server[:port] β€” the hostname or IP address of the remote server. optionally you can specify a UDP port. if you don't specify one, it gets looked up in /etc/services. the service name it looks for is radacct for accounting packets, and radius for all other requests. and if that service isn't found in /etc/services? then 1813 and 1812 are used respectively. 🌈
  • secret β€” the shared secret for this client. it needs to be defined on the radius server side too, for the IP address you're sending the radius packets from. like, it takes two, fr fr. 🀝

πŸ”₯ SEE ALSO πŸ”₯

radwho(1), radclient(1), radiusd(8), radiusd.conf(5).

go read those too, bestie, they're iconic in their own right. πŸ“šβœ¨


🌟 AUTHOR 🌟

Alan DeKok <aland@ox.org> πŸ’–


and that's the whole page!! πŸŽ€ this version of RADZAP(1) is from the FreeRADIUS Daemon source, dated 8 April 2005. bye bestie, go zap responsibly πŸ’…πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from