Realm: pkc.gov.uk Full
pkc.gov.uk/pkc-gov-uk-0/NRPS: roaming0.govroam.uk
(212.219.190.139) -
Unknown Client
/
Port 1812 Drop
/
Bad Client Shared Secret
/
pkc.gov.uk/pkc-gov-uk-0/roaming0.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 21.72 ms
- Last State Change
- Tue Apr 7 07:28:26 2026
- Last Check
- Mon Apr 13 09:08:17 2026
- Next Check
- Mon Apr 13 09:18:17 2026
pkc.gov.uk/pkc-gov-uk-0/roaming0.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Fri Apr 10 17:56:17 2026
- Last Check
- Mon Apr 13 09:06:15 2026
- Next Check
- Mon Apr 13 09:16:15 2026
pkc.gov.uk/pkc-gov-uk-0/roaming0.govroam.uk/
Server Shared Secret
- Output
- OK: Good shared secret over last day
- Last State Change
- Sun Apr 12 16:36:17 2026
- Last Check
- Mon Apr 13 09:06:15 2026
- Next Check
- Mon Apr 13 09:16:15 2026
pkc.gov.uk/pkc-gov-uk-0/roaming0.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Apr 7 07:28:04 2026
- Last Check
- Mon Apr 13 09:06:00 2026
- Next Check
- Mon Apr 13 09:16:00 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
pkc.gov.uk/pkc-gov-uk-0/roaming0.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Wed Apr 8 13:27:40 2026
- Last Check
- Mon Apr 13 09:07:38 2026
- Next Check
- Mon Apr 13 09:17:38 2026
pkc.gov.uk/pkc-gov-uk-0/NRPS: roaming1.govroam.uk
(212.219.209.43) -
Unknown Client
/
Port 1812 Drop
/
Bad Client Shared Secret
/
pkc.gov.uk/pkc-gov-uk-0/roaming1.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 21.56 ms
- Last State Change
- Tue Apr 7 07:22:39 2026
- Last Check
- Mon Apr 13 09:02:28 2026
- Next Check
- Mon Apr 13 09:12:28 2026
pkc.gov.uk/pkc-gov-uk-0/roaming1.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Fri Apr 10 18:14:45 2026
- Last Check
- Mon Apr 13 09:04:43 2026
- Next Check
- Mon Apr 13 09:14:43 2026
pkc.gov.uk/pkc-gov-uk-0/roaming1.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Tue Apr 7 07:23:22 2026
- Last Check
- Mon Apr 13 09:01:21 2026
- Next Check
- Mon Apr 13 09:11:21 2026
pkc.gov.uk/pkc-gov-uk-0/roaming1.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Apr 7 07:24:01 2026
- Last Check
- Mon Apr 13 09:01:58 2026
- Next Check
- Mon Apr 13 09:11:57 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
pkc.gov.uk/pkc-gov-uk-0/roaming1.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Tue Apr 7 07:24:24 2026
- Last Check
- Mon Apr 13 09:02:23 2026
- Next Check
- Mon Apr 13 09:12:23 2026
pkc.gov.uk/pkc-gov-uk-0/NRPS: roaming2.govroam.uk
(212.219.247.59) -
Unknown Client
/
Port 1812 Drop
/
Bad Client Shared Secret
/
pkc.gov.uk/pkc-gov-uk-0/roaming2.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 15.05 ms
- Last State Change
- Tue Apr 7 07:16:38 2026
- Last Check
- Mon Apr 13 09:06:28 2026
- Next Check
- Mon Apr 13 09:16:28 2026
pkc.gov.uk/pkc-gov-uk-0/roaming2.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Fri Apr 10 18:02:15 2026
- Last Check
- Mon Apr 13 09:02:13 2026
- Next Check
- Mon Apr 13 09:12:12 2026
pkc.gov.uk/pkc-gov-uk-0/roaming2.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Tue Apr 7 07:20:35 2026
- Last Check
- Mon Apr 13 09:08:33 2026
- Next Check
- Mon Apr 13 09:18:33 2026
pkc.gov.uk/pkc-gov-uk-0/roaming2.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Apr 7 07:18:41 2026
- Last Check
- Mon Apr 13 09:06:37 2026
- Next Check
- Mon Apr 13 09:16:37 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
pkc.gov.uk/pkc-gov-uk-0/roaming2.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Tue Apr 7 07:21:05 2026
- Last Check
- Mon Apr 13 09:09:03 2026
- Next Check
- Mon Apr 13 09:19:03 2026
pkc.gov.uk/pkc-gov-uk-0/NRPS: roaming3.govroam.uk
(195.194.21.203) -
Unknown Client
/
Port 1812 Drop
/
Bad Client Shared Secret
/
pkc.gov.uk/pkc-gov-uk-0/roaming3.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 15.35 ms
- Last State Change
- Tue Apr 7 07:17:25 2026
- Last Check
- Mon Apr 13 09:07:16 2026
- Next Check
- Mon Apr 13 09:17:16 2026
pkc.gov.uk/pkc-gov-uk-0/roaming3.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Sun Apr 12 17:16:36 2026
- Last Check
- Mon Apr 13 09:06:35 2026
- Next Check
- Mon Apr 13 09:16:35 2026
pkc.gov.uk/pkc-gov-uk-0/roaming3.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Tue Apr 7 07:17:03 2026
- Last Check
- Mon Apr 13 09:05:01 2026
- Next Check
- Mon Apr 13 09:15:01 2026
pkc.gov.uk/pkc-gov-uk-0/roaming3.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Apr 7 07:16:06 2026
- Last Check
- Mon Apr 13 09:04:02 2026
- Next Check
- Mon Apr 13 09:14:02 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
pkc.gov.uk/pkc-gov-uk-0/roaming3.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Sun Apr 12 18:27:11 2026
- Last Check
- Mon Apr 13 09:07:10 2026
- Next Check
- Mon Apr 13 09:17:09 2026
Called Station ID Check
- Output
- WARNING: 51% Lower case characters in MAC (last: 2026-04-13 08:40:54). 51% Missing SSID, as of 2026-04-13 08:40:54. 51% MAC format wrong - uses ':' not '-' as separator (last: 2026-04-13 08:40:54)
- Last State Change
- Mon Apr 13 06:55:17 2026
- Last Check
- Mon Apr 13 08:55:16 2026
- Next Check
- Mon Apr 13 09:10:15 2026
- Meaning:
-
The Called-Station-ID contains the MAC address of the device the client
connects to as well as, potentially, the SSID of the wireless network it
connected to. The format of the MAC address is specified in RFC
3580 as
'XX-XX-XX-XX-XX-XX:SSID' with '-' being the only valid separator and all
upper case. The SSID should be appended.
Having the Called-Station-ID included in proxied requests makes it possible to ensure that the SSID being broadcast matches the service requirements. - Solution:
- Configure your wireless system to provide the CSI in the RFC3580 format.
Calling Station ID Check
- Output
- WARNING: 51% MAC format wrong, contains lower case (last: 2026-04-13 08:40:54). 51% MAC format wrong, does not use '-' as separator (last: 2026-04-13 08:40:54)
- Last State Change
- Mon Apr 13 06:53:28 2026
- Last Check
- Mon Apr 13 09:08:27 2026
- Next Check
- Mon Apr 13 09:23:26 2026
- Meaning:
- Calling Station ID identifies the device making the connection and RFC 3580 states that the format should be XX-XX-XX-XX-XX-XX (i.e. '-' separated and upper case).
- Solution:
- Configure your wireless system to use upper case and '-' separated pairs.
Operator Check
- Output
- OK: 100% Operator-Name present (last: 2026-04-13 08:43:55)
- Last State Change
- Sun Apr 12 16:40:18 2026
- Last Check
- Mon Apr 13 08:55:16 2026
- Next Check
- Mon Apr 13 09:10:14 2026
Realm Syntax Check
- Output
- CRITICAL: 70.4% Non word (a-zA-Z0-9.-) chars in realm (last: 2026-04-13 08:43:55)
- Last State Change
- Mon Apr 13 06:47:49 2026
- Last Check
- Mon Apr 13 09:02:48 2026
- Next Check
- Mon Apr 13 09:17:47 2026
- Meaning:
- The syntax of a realm proxied does not match what's acceptable. A realm should be in the format of 'realm.tld' or 'something.site.tld' and shouldn't have '..' or start or end with '.', shouldn't contain characters other than '0-9a-zA-Z-.', shouldn't be empty or missing. Since these realms are entered by end-users typos are possible. Obviously the NRPS should never see the site's own realm proxied as that could cause loops.
- Solution:
- Filter out syntactically invalid realms, don't proxy them.
VLAN Check
- Output
- OK: 100% No VLAN attr present (last: 2026-04-13 08:43:55)
- Last State Change
- Sun Apr 12 16:39:52 2026
- Last Check
- Mon Apr 13 08:54:50 2026
- Next Check
- Mon Apr 13 09:09:49 2026