RADIUM(8)

💖 RADIUM(8) 💖

okay bestie, welcome to radium(8) from the System Manager's Manual — yes this is section 8, daemon territory, main character energy only 🌈

---

✨ NAME ✨

radium — the argus record multiplexor. that's it, that's the name 🎀

---

🌸 SYNOPSIS 🌸

radium [ options ] [ raoptions ]

look at that. so clean. so simple. the options go here, the raoptions go there 🦋

---

💅 DESCRIPTION 💅

So like, Radium is a real-time Argus Record multiplexor, and what it does is process Argus records and Netflow records, then output them to literally any number of client programs and files. it's a combination of the features of ra.1 and argus.8, and it supports access for upto 128 client programs to argus records coming from remote data sources and/or local managed argus data files. with radium you can construct complex distribution networks for collecting and processing argus data, and provide a single point of access to archived argus data. it's giving infrastructure icon 👑

Designed to run as a daemon, radium generally reads argus records directly from a remote argus, and writes the transaction status information to a log file or open socket connected to an argus client (such as ra(1)). Radium provides the same data access controls as argus.8, including remote filtering, source address based access control, indivual oriented strong authentication and confidentiality protection for the distributed data, using SASL and tcp_wrapper technology. please refer to the INSTALL and README files for each distribution for a complete description, fr fr 📚

Radium is normally configured from a system /etc/radium.conf configuration file, or from a configuration file either in the $RADIUMHOME directory, or specified on the command line. options, options, options ✨

---

🔥 RADIUM SPECIFIC OPTIONS 🔥

Radium, like all ra based clients, supports a number of ra options including remote data access, reading from multiple files and filtering of input argus records through a terminating filter expression. but the radium(8) specific options are the ones we're here for, so let's go 🫶

---

👑 OPTIONS 👑

• -B <addr> — specify the bind interface address for remote access. acceptable values are IP version 4 addresses. the default is to bind to INADDR_ANY address. so like, the default is everything, bestie 🌐
• -d — run radium as a daemon. this will cause radium to do the things that Unix daemons do and return, if there were no errors, with radium running as a detached process. it's leaving the group chat but staying online 💀
• -e <value> — specify the source identifier for this radium. acceptable values are numbers, hostnames or ip address. name your child 🍼
• -f <radium.conf> — use radium.conf as a source of configuration information. options set in this file override any other specification, and so this is the last word on option values. this file is read after the system /etc/radium.conf file is processed. see radium.conf.5 for the configuration file format. it said what it said and it will not be taking questions 💅
• -O — turn off Berkeley Packet Filter optimizer. no reason to do this unless you think the optimizer generates bad code. lowkey don't 🚩
• -p — override the persistent connection facility. Radium provides a fault tolerant feature for its remote argus data access facility. if the remote argus data source closes, radium will maintain its client connections, and attempt to reestablish its connection with remote source. this option overrides this behavior, causing radium to terminate if any of its remote sources closes. so instead of being chill and reconnecting, it just ✨perishes✨ 😭
• -P <portnum> — specifies the <portnum> for remote client connection. the default is to not support remote access. setting the value to zero (0) will forceably turn off the facility. zero means no, and it means it forcefully 🚫
• -S <host[:port][//full/path/to/argus.data.file]> — attach to a specific remote host to receive argus records. append an optional port specifier to attach to a port value other than the default 561. without the optional full pathname, radium will continuously transmit a stream of real-time flow records as they are received. with the optional filename, radium will open the argus datafile specified, and stream the contents, closing the connection with the file EOF. pick your fighter: live stream or reading the archive 📖
• -T threshold[smh] (secs) — indicate that radium should correct the timestamps of received argus records, if they are out of sync by threshold secconds. threshold can be specified with the extensions s, m, or h for seconds, minutes or hours. clock drift? not on our watch ⏰
• -X — clear existing radium configuration. this removes any initialization done prior to encountering this flag. allows you to eliminate the effects of the /etc/radium.conf file, or any radium.conf files that may have been loaded. the ultimate "new phone who dis" 📵

---

🌟 SIGNALS 🌟

Radium catches a number of signal(3) events. the three signals SIGHUP, SIGINT, and SIGTERM cause radium to exit, writing TIMEDOUT status records for all currently active transactions. the signal SIGUSR1 will turn on debug reporting, and subsequent SIGUSR1 signals will increment the debug-level. the signal SIGUSR2 will cause radium to turn off all debug reporting. so basically SIGUSR1 is the "tell me more" button and SIGUSR2 is the "okay that's enough" button 🙈

---

🦋 ENVIRONMENT 🦋

• $RADIUMHOME — Radium Root directory 🏠
• $RADIUMPATH — Radium.conf search path (/etc:$RADIUMHOME:$HOME) 🔍

---

🎀 FILES 🎀

• /etc/radium.conf — radium daemon configuration file
• /var/run/radium.#.#.pid — PID file

---

🌈 EXAMPLES 🌈

Run radium as a daemon, reading records from a remote host, using port 561, and writing all its transaction status reports to output-file. this is a typical mode.

radium -S remotehost:561 -d -e `hostname` -w output-file

Collect records from multiple argi, using port 561 on one and port 430 on the other, and make all of these records available to other programs on port 562.

radium -S host1:561 -S host2:430 -de `hostname` -P 562

Collect records from multiple Cisco Netflow sources, using the default port, and make the resulting argus records available on port 562.

radium -C -S host1 -S host2 -de `hostname` -P 562

Radium supports both input filtering and output filtering, and radium supports multiple output streams, each with their own independant filters. so many streams, so many filters, we love a multitasker 💖

If you are interested in distributing IP traffic only (input filter) and want to separate traffic into differing files based on traffic type, this simple example separates ICMP traffic from other traffic.

radium -w file1 "icmp" -w file2 "not icmp" - ip

Audit the network activity that is flowing between the two gateway routers, whose ethernet addresses are 00:08:03:2D:42:01 and 00:00:0C:18:29:F1. make records available to other programs through port 430/tcp.

radium -S source -P 430 - ether host (0:8:3:2d:42:1 and 0:0:c:18:29:f1) &

Process argus records from a remote source only between 9am and 5pm every day and provide access to this stream on port 562.

radium -S remotehost -t 9-17 -P 562

---

💜 COPYRIGHT 💜

Copyright (c) 2000-2024 QoSient, LLC All rights reserved.

---

🫶 AUTHORS 🫶

Carter Bullard (carter@qosient.com)

---

⭐ SEE ALSO ⭐

radium.conf(5), argus(8), hosts_access(5), hosts_options(5), tcpd(8), tcpdump(1)

---

and that's the whole thing bestie, we ate and left absolutely no crumbs 👑

this was radium 5.0.3, dated 21 October 2016 — yeah she's vintage, she's iconic, she's still running your network. periodt 💅✨