Realm: pkc.gov.uk Full

pkc.gov.uk/ORPS: pkc-gov-uk-0
pkc.gov.uk/pkc-gov-uk-0/NRPS: roaming0.govroam.uk (212.219.190.139) - Port 1812 Drop / Bad Client Shared Secret / Unknown Client /
pkc.gov.uk/pkc-gov-uk-0/roaming0.govroam.uk/ Ping
Output
PING OK - Packet loss = 0%, RTA = 21.54 ms
Last State Change
Thu Jul 3 11:56:22 2025
Last Check
Sun Jul 13 15:16:12 2025
Next Check
Sun Jul 13 15:26:12 2025
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
Thu Jul 3 11:52:39 2025
Last Check
Sun Jul 13 15:12:37 2025
Next Check
Sun Jul 13 15:22:37 2025
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 Jul 6 14:34:02 2025
Last Check
Sun Jul 13 15:14:01 2025
Next Check
Sun Jul 13 15:24:01 2025
pkc.gov.uk/pkc-gov-uk-0/roaming0.govroam.uk/ Simple Authentication
Output
WARNING: Timeout. No response from RADIUS server
Last State Change
Thu Jul 3 11:54:33 2025
Last Check
Sun Jul 13 15:12:30 2025
Next Check
Sun Jul 13 15:22:30 2025
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
Sat Jul 12 13:13:15 2025
Last Check
Sun Jul 13 15:13:14 2025
Next Check
Sun Jul 13 15:23:14 2025
pkc.gov.uk/pkc-gov-uk-0/NRPS: roaming1.govroam.uk (212.219.209.43) - Port 1812 Drop / Bad Client Shared Secret / Unknown Client /
pkc.gov.uk/pkc-gov-uk-0/roaming1.govroam.uk/ Ping
Output
PING OK - Packet loss = 0%, RTA = 21.40 ms
Last State Change
Thu Jul 3 11:54:57 2025
Last Check
Sun Jul 13 15:14:47 2025
Next Check
Sun Jul 13 15:24:47 2025
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
Thu Jul 3 11:58:13 2025
Last Check
Sun Jul 13 15:18:11 2025
Next Check
Sun Jul 13 15:28:11 2025
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
Thu Jul 3 11:54:35 2025
Last Check
Sun Jul 13 15:12:32 2025
Next Check
Sun Jul 13 15:22:32 2025
pkc.gov.uk/pkc-gov-uk-0/roaming1.govroam.uk/ Simple Authentication
Output
WARNING: Timeout. No response from RADIUS server
Last State Change
Thu Jul 3 11:57:47 2025
Last Check
Sun Jul 13 15:15:44 2025
Next Check
Sun Jul 13 15:25:44 2025
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
Thu Jul 3 11:56:05 2025
Last Check
Sun Jul 13 15:14:04 2025
Next Check
Sun Jul 13 15:24:04 2025
pkc.gov.uk/pkc-gov-uk-0/NRPS: roaming2.govroam.uk (212.219.247.59) - Port 1812 Drop / Bad Client Shared Secret / Unknown Client /
pkc.gov.uk/pkc-gov-uk-0/roaming2.govroam.uk/ Ping
Output
PING OK - Packet loss = 0%, RTA = 15.14 ms
Last State Change
Thu Jul 3 11:55:39 2025
Last Check
Sun Jul 13 15:15:29 2025
Next Check
Sun Jul 13 15:25:29 2025
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
Thu Jul 3 11:58:40 2025
Last Check
Sun Jul 13 15:18:39 2025
Next Check
Sun Jul 13 15:28:39 2025
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
Thu Jul 3 11:57:31 2025
Last Check
Sun Jul 13 15:15:30 2025
Next Check
Sun Jul 13 15:25:30 2025
pkc.gov.uk/pkc-gov-uk-0/roaming2.govroam.uk/ Simple Authentication
Output
WARNING: Timeout. No response from RADIUS server
Last State Change
Thu Jul 3 11:59:18 2025
Last Check
Sun Jul 13 15:17:14 2025
Next Check
Sun Jul 13 15:27:14 2025
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
Thu Jul 3 11:59:22 2025
Last Check
Sun Jul 13 15:17:21 2025
Next Check
Sun Jul 13 15:27:21 2025
pkc.gov.uk/pkc-gov-uk-0/NRPS: roaming3.govroam.uk (195.194.21.203) - Port 1812 Drop / Bad Client Shared Secret / Unknown Client /
pkc.gov.uk/pkc-gov-uk-0/roaming3.govroam.uk/ Ping
Output
PING OK - Packet loss = 0%, RTA = 15.41 ms
Last State Change
Thu Jul 3 11:57:57 2025
Last Check
Sun Jul 13 15:17:47 2025
Next Check
Sun Jul 13 15:27:47 2025
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
Thu Jul 3 11:56:58 2025
Last Check
Sun Jul 13 15:16:56 2025
Next Check
Sun Jul 13 15:26:56 2025
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
Thu Jul 3 11:58:44 2025
Last Check
Sun Jul 13 15:16:42 2025
Next Check
Sun Jul 13 15:26:42 2025
pkc.gov.uk/pkc-gov-uk-0/roaming3.govroam.uk/ Simple Authentication
Output
WARNING: Timeout. No response from RADIUS server
Last State Change
Thu Jul 3 11:59:45 2025
Last Check
Sun Jul 13 15:17:42 2025
Next Check
Sun Jul 13 15:27:42 2025
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
Thu Jul 3 11:59:27 2025
Last Check
Sun Jul 13 15:17:26 2025
Next Check
Sun Jul 13 15:27:26 2025
Called Station ID Check
Output
WARNING: 42% Lower case characters in MAC (last: 2025-07-12 21:00:00). 42% Missing SSID, as of 2025-07-12 21:00:00. 42% MAC format wrong - uses ':' not '-' as separator (last: 2025-07-12 21:00:00)
Last State Change
Mon Jul 7 07:11:18 2025
Last Check
Sun Jul 13 15:11:16 2025
Next Check
Sun Jul 13 15:26:14 2025
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: 42% MAC format wrong, contains lower case (last: 2025-07-12 21:00:00). 42% MAC format wrong, does not use '-' as separator (last: 2025-07-12 21:00:00)
Last State Change
Mon Jul 7 07:12:18 2025
Last Check
Sun Jul 13 15:12:17 2025
Next Check
Sun Jul 13 15:27:15 2025
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: 2025-07-13 09:13:09)
Last State Change
Sun Jul 6 14:34:24 2025
Last Check
Sun Jul 13 15:19:23 2025
Next Check
Sun Jul 13 15:34:21 2025
Realm Syntax Check
Output
OK: 100.0% Good syntax (last: 2025-07-13 09:13:09)
Last State Change
Sat Jul 12 15:03:34 2025
Last Check
Sun Jul 13 15:18:32 2025
Next Check
Sun Jul 13 15:33:31 2025
VLAN Check
Output
OK: 100% No VLAN attr present (last: 2025-07-13 09:13:09)
Last State Change
Sun Jul 6 14:33:22 2025
Last Check
Sun Jul 13 15:18:20 2025
Next Check
Sun Jul 13 15:33:19 2025