If no RADIUS information is shown in the BQN GUI, to check if RADIUS messages are incoming, log as root in BQN UNIX shell and run the following command:

# tcpdump -i eno1 'udp and port 1813’
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eno1, link-type EN10MB (Ethernet), capture size 65535 bytes

In this example, the management interface is eno1. Check the one of your BQN server in Configuration->Interfaces->Management (the 0 added by BQN configuration must be removed, for example, en0s1f0in BQN GUI is ens1f0 in Linux).

If the BQN firewall is configured (Configuration->Interfaces->Management Firewall), all RADIUS client IPs must be added (in this example,10.10.10.10 y 10.10.10.11).

And now the RADIUS messages are received:

#  tcpdump -i eno1 'udp and port 1813’
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eno1, link-type EN10MB (Ethernet), capture size 65535 bytes
14:21:20.177347 IP 10.10.10.10.60072 > 192.168.0.121.radius-acct: RADIUS, Accounting Request (4), id: 0xf0 length: 222
14:21:20.177424 IP 192.168.0.121.radius-acct > 10.10.10.10.60072: RADIUS, Accounting Response (5), id: 0xf0 length: 20
. . .

If RADIUS messages are still no received, the rest of the traffic jumps need verification. In our example, RADIUS clients are in subnet10.10.10.0/24 and BQN in subnet 192.168.0.0/24. It has to be verified if there are valid routes between the two subnets and that no intermediate firewall is blocking UDP port 1813 (RADIUS Accounting).

‍