Configuration & monitoring
A RADIUS proxy context is defined by where it forwards traffic, how that traffic is secured, and what attributes it returns. Because identities live in the remote federation, the local configuration is concerned with relaying and observing traffic rather than with managing users.
Remote RADIUS server
Section titled “Remote RADIUS server”The upstream server is the federation’s RADIUS proxy — for example a national eduroam proxy. It is defined by:
| Setting | Value |
|---|---|
| Hostname or IP | The remote authentication server |
| Authentication port | UDP 1812 |
| Accounting port | UDP 1813 |
| Shared secret | Secures the link between the EntryPoint context and the remote server |
RadSec
Section titled “RadSec”Where the remote server supports it, RadSec carries the forwarded RADIUS inside a TLS tunnel, encrypting the traffic and verifying the remote server’s identity — valuable over public or semi-trusted paths. Trusted CA certificates validate the remote server, and a client certificate is provided where mutual authentication is required. Certificate formats are covered in Certificates & PKI.
Default device group and attribute profiles
Section titled “Default device group and attribute profiles”A proxy context provisions a single default device group that handles all incoming requests. Attribute Profiles attached to it shape the RADIUS response — for example assigning a VLAN through Tunnel-Type, Tunnel-Medium-Type, and Tunnel-Private-Group-ID, or a vendor-specific attribute — so roaming users land on the correct local network.
Network integration
Section titled “Network integration”The local side defines the ports for authentication, accounting, and RadSec, the client secret the local equipment uses, and an optional restriction of which source ranges may reach the context. This is the same model as any other context — see RADIUS clients & RadSec.
Monitoring
Section titled “Monitoring”The context reports the number of registered devices and how many are currently online, and a usage view shows registration and activity trends over time. Individual device records show MAC address, associated group, IP address, and first- and last-seen times, which helps with troubleshooting roaming access and understanding utilisation.
Related sections
Section titled “Related sections”- eduroam / RADIUS Proxy overview.
- RADIUS clients & RadSec and Certificates & PKI.
- Authentication log: per-attempt outcomes for forwarded requests.