NAC
This page describes how the NAC module works with FreeRADIUS, what devices and COD need for it and where the limits are.
What the module does is described on the module page.
As of: November 2026, COD 3.8.6
Documentation contents
- Overview
- Getting started
- Requirements
- Names and addresses
- Network devices
- Time and DNS
- Installation
- Deployment shapes
- Initial setup
- Updates
- Modules
- Network and MikroTik
- Automation
- NAC
- TACACS+
- Firewall
- Captive Portal
- Monitoring
- Backup
- Hypervisor
- OTP
- Passkeepr
- GRC
- Inventory and CMDB import
- Troubleshooting
- Security
- Versions
- Version history
- Support
Documentation
- Overview
- Getting started
- Requirements
- Names and addresses
- Network devices
- Time and DNS
- Installation
- Deployment shapes
- Initial setup
- Updates
- Modules
- Network and MikroTik
- Automation
- NAC
- TACACS+
- Firewall
- Captive Portal
- Monitoring
- Backup
- Hypervisor
- OTP
- Passkeepr
- GRC
- Inventory and CMDB import
- Troubleshooting
- Security
- Versions
- Version history
- Support
Overview
| Item | Value |
|---|---|
| Purpose | Interface and control for FreeRADIUS: MAC authentication (MAB), 802.1X with EAP-TLS, dynamic VLAN assignment, NAS management, built-in certificate authority |
| Devices | Switches and access points with 802.1X or MAC authentication and RADIUS, vendor-independent |
| Service | NAC service with FreeRADIUS and its own database. On the COD server or on a separate server, once per host |
| Connections and direction | Device to NAC server: RADIUS authentication and RADIUS accounting. NAC server to device: disconnect request (CoA) and ICMP for heartbeat and test. COD to NAC service: all calls from the interface |
| Credentials | Shared secret per NAS, entered identically on the device |
| Firewall rules | Customers and partners receive the list of connections and firewall rules as part of the project. |
If the NAC service runs on a separate server, for example close to the network devices: the connection between COD and module servers belongs in a trusted network. With Private Hosted, you provide and operate the NAC component in your own network.
Requirements
On the switch or access point
| Requirement | Why |
|---|---|
| 802.1X or MAC authentication (MAB) with RADIUS | Basis of access control |
| NAC server as RADIUS server, shared secret as in the NAS entry | Without a matching secret, FreeRADIUS rejects the request |
| RADIUS source address equals the device’s management address | Otherwise no NAC sessions appear at the port in Network |
| Send RADIUS accounting to the NAC server | Sessions and connection statistics |
| Accept disconnect requests (CoA) from the NAC server | Ending a session from COD, secret test |
For Allied Telesis, Cisco and Ruijie an auth profile rolls out the 802.1X and RADIUS lines. See Automation.
In COD and on the host
- NAC module enabled for the tenant.
- NAC service rolled out for the location.
- Time sync via NTP on the NAC server. See Time and DNS.
- Optional: mail setting of the NAC service for notifications.
Setup
- Enable the module with the Manager account under “Admin Area > Tenant > Modules”. Then log out and log in again.
- Roll out the NAC service under “Admin Area > Module Rollout”: NAC module, location, then Install, Connect, Configure and Apply.
- Create or import a CA. Issue the server certificate. COD rolls it out to FreeRADIUS.
- Add each switch and access point as a NAS with a shared secret.
- COD then reports that FreeRADIUS needs a restart. “Restart Now” restarts FreeRADIUS without asking on all NAC servers of the location. Choose the moment deliberately.
- Set up RADIUS on the device: server, shared secret, source address, accounting.
- Create VLANs, client groups with priorities and MAC entries. Import larger sets by CSV.
- For 802.1X: issue client certificates and distribute them as PKCS#12.
- Check logins in the authentication and accounting logs and the sessions under the port card in Network.
Note: “Test Connection” sends a real disconnect request to the device. Run the test when a dropped session does not bother anyone.
Technical details
| Item | Value |
|---|---|
| Type | COD-native, vendor-independent NAC solution based on FreeRADIUS |
| Authentication | 802.1X with EAP-TLS (certificates), MAC authentication (MAB) |
| EAP methods | defined by the FreeRADIUS configuration on the host. The interface has no EAP settings |
| Access control | dynamic VLAN assignment with the RADIUS attributes Tunnel-Private-Group-Id, Cisco-AVPair and Egress-VLANID. Client groups with priorities |
| PKI | CAs with RSA, ECDSA or EdDSA, leaf certificates with SANs, CRL, PKCS#12 export, CSV import of existing stock. Server certificates go to FreeRADIUS automatically, COD detects new CAs by itself |
| NAS management | switches and access points with shared secret |
| Logging | authentication and accounting logs (success, failure, sessions), connection statistics per client, optional log streaming |
| Import | CSV bulk import of MAC addresses, VLAN assignments and groups with validation and conflict detection |
| Time-based access | guests and temporary staff get onto the network only within the defined time window |
| Service control | start, stop and restart of FreeRADIUS in the interface, with status and uptime |
| Audit | changes in the NAC service appear in the Admin Area audit, with the user who made them |
| Forwarding | optionally logs via GELF to Graylog, sent from the NAC server |
VLAN assignment
A device can be assigned to any VLAN you have created, including a dedicated quarantine or guest VLAN. The module does not check whether an endpoint is compliant.
Sessions at the port
Under the port card, Network shows the device’s RADIUS sessions: user, MAC, IP, start, duration and end. COD asks NAC for this in every common spelling of port and MAC. This requires the switch to send RADIUS from its management address.
Who was connected and when
The authentication and accounting logs and the per-client connection statistics show this.
Known limits
| Limit | What you can do |
|---|---|
| The NAS list is not linked to the asset | If a device’s address changes, update the NAS entry by hand |
| “Test Connection” sends a real disconnect request | Test when a dropped session does not bother anyone |
| With several NAC instances, the configuration reaches only the first one that answers | Do not expect synchronisation between instances. Plan redundancy with your partner |
| NAC runs once per host | A further instance needs a host of its own |
| No EAP settings in the interface | The FreeRADIUS configuration defines the EAP methods. Agree on changes with your partner |
| “Restart Now” restarts without asking on all NAC servers of the location | Restart when short login gaps do not bother anyone |
| No NAC sessions at the port if the RADIUS source address is not the management address | Set the source address on the device to the management address |
| No connection to an existing Windows CA | Use COD’s certificate authority for 802.1X |
| No connection to PacketFence | Network access control in COD works with FreeRADIUS |
| No compliance check of endpoints | Assign suspicious devices to a quarantine VLAN |
Further reading
- NAC module page
- What your network needs for NAC
- Auth profiles with the Automation module
- Deployment shapes with a separate NAC server
- Troubleshooting
- Questions about the modules
- Support: your partner is your first point of contact. Technical questions to extocode go through the helpdesk form.