# RADIUS accounting

The other protocols on this section connect OpenGate to a **device**. RADIUS connects it to the **network**:
the platform can receive RADIUS accounting packets from Remote Access Servers or delegated RADIUS servers,
and learn the operational state of M2M communications from the operator side rather than from the device.

That matters because it answers questions the device cannot. A device that stopped reporting looks identical
whether it is broken, out of coverage, or its SIM was suspended — network-side accounting tells them apart.

## Who sends what

| | |
|---|---|
| Sender | GGSN nodes, Remote Access Servers, or delegated RADIUS servers |
| Carries | RADIUS **accounting** packets about network sessions |
| Direction | Into OpenGate: the node reports, the platform receives |

Gateway GPRS support nodes are part of the mobile operator's network and are the usual source, which is why
this is provisioned as a mobile-operator concern rather than a device one.

## Where it is provisioned

RADIUS clients are registered under mobile operators, not per device or channel:

**[Management › Mobile operators › GGSN](../../management/mobile_operators/ggsn/)**

That page holds the API to provision the RADIUS clients allowed to forward accounting to the platform, and
its OpenAPI specification.

{{% notice style="note" title="Limited access" icon="lock" %}}
Provisioning RADIUS clients is a restricted feature. See the GGSN page for the profiles required.
{{% /notice %}}

## Where to go next

| To | Read |
|---|---|
| See every protocol OpenGate speaks | [Supported protocols](../supported_protocols/) |
| Provision the RADIUS clients | [GGSN](../../management/mobile_operators/ggsn/) |
| Manage the SIMs behind those sessions | [Mobile operators](../../management/mobile_operators/) |