Realm: behmht.net Full
behmht.net/behmht-net-0/NRPS: roaming0.govroam.uk
(212.219.190.139) -
Unknown Client
/
Port 1812 Drop
/
Bad Client Shared Secret
/
Dropping Auth Requests
/
behmht.net/behmht-net-0/roaming0.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 12.73 ms
- Last State Change
- Thu Dec 12 11:33:25 2024
- Last Check
- Thu Dec 12 21:03:15 2024
- Next Check
- Thu Dec 12 21:13:15 2024
behmht.net/behmht-net-0/roaming0.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Dec 12 11:33:25 2024
- Last Check
- Thu Dec 12 21:03:24 2024
- Next Check
- Thu Dec 12 21:13:24 2024
behmht.net/behmht-net-0/roaming0.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Dec 12 11:34:29 2024
- Last Check
- Thu Dec 12 21:02:28 2024
- Next Check
- Thu Dec 12 21:12:28 2024
behmht.net/behmht-net-0/roaming0.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Dec 12 11:35:36 2024
- Last Check
- Thu Dec 12 21:03:37 2024
- Next Check
- Thu Dec 12 21:13:35 2024
- 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).
behmht.net/behmht-net-0/roaming0.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Thu Dec 12 11:33:23 2024
- Last Check
- Thu Dec 12 21:01:22 2024
- Next Check
- Thu Dec 12 21:11:21 2024
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
behmht.net/behmht-net-0/NRPS: roaming1.govroam.uk
(212.219.209.43) -
Unknown Client
/
Port 1812 Drop
/
Bad Client Shared Secret
/
Dropping Auth Requests
/
behmht.net/behmht-net-0/roaming1.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 12.53 ms
- Last State Change
- Thu Dec 12 11:36:51 2024
- Last Check
- Thu Dec 12 21:06:41 2024
- Next Check
- Thu Dec 12 21:16:41 2024
behmht.net/behmht-net-0/roaming1.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Dec 12 11:34:47 2024
- Last Check
- Thu Dec 12 21:04:46 2024
- Next Check
- Thu Dec 12 21:14:46 2024
behmht.net/behmht-net-0/roaming1.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Dec 12 11:36:32 2024
- Last Check
- Thu Dec 12 21:04:31 2024
- Next Check
- Thu Dec 12 21:14:31 2024
behmht.net/behmht-net-0/roaming1.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Dec 12 11:36:20 2024
- Last Check
- Thu Dec 12 21:04:19 2024
- Next Check
- Thu Dec 12 21:14:19 2024
- 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).
behmht.net/behmht-net-0/roaming1.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Thu Dec 12 12:14:59 2024
- Last Check
- Thu Dec 12 21:04:58 2024
- Next Check
- Thu Dec 12 21:14:58 2024
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
behmht.net/behmht-net-0/NRPS: roaming2.govroam.uk
(212.219.247.59) -
Unknown Client
/
Port 1812 Drop
/
Bad Client Shared Secret
/
behmht.net/behmht-net-0/roaming2.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 5.82 ms
- Last State Change
- Thu Dec 12 11:35:15 2024
- Last Check
- Thu Dec 12 21:05:05 2024
- Next Check
- Thu Dec 12 21:15:05 2024
behmht.net/behmht-net-0/roaming2.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Dec 12 11:37:16 2024
- Last Check
- Thu Dec 12 21:07:14 2024
- Next Check
- Thu Dec 12 21:17:14 2024
behmht.net/behmht-net-0/roaming2.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Dec 12 11:35:45 2024
- Last Check
- Thu Dec 12 21:03:44 2024
- Next Check
- Thu Dec 12 21:13:44 2024
behmht.net/behmht-net-0/roaming2.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Dec 12 11:37:50 2024
- Last Check
- Thu Dec 12 21:05:48 2024
- Next Check
- Thu Dec 12 21:15:48 2024
- 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).
behmht.net/behmht-net-0/roaming2.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Thu Dec 12 11:36:40 2024
- Last Check
- Thu Dec 12 21:04:38 2024
- Next Check
- Thu Dec 12 21:14:38 2024
behmht.net/behmht-net-0/NRPS: roaming3.govroam.uk
(195.194.21.203) -
Unknown Client
/
Port 1812 Drop
/
Bad Client Shared Secret
/
behmht.net/behmht-net-0/roaming3.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 6.05 ms
- Last State Change
- Thu Dec 12 11:33:49 2024
- Last Check
- Thu Dec 12 21:03:38 2024
- Next Check
- Thu Dec 12 21:13:38 2024
behmht.net/behmht-net-0/roaming3.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Dec 12 11:36:44 2024
- Last Check
- Thu Dec 12 21:06:42 2024
- Next Check
- Thu Dec 12 21:16:42 2024
behmht.net/behmht-net-0/roaming3.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Dec 12 11:34:03 2024
- Last Check
- Thu Dec 12 21:02:01 2024
- Next Check
- Thu Dec 12 21:12:01 2024
behmht.net/behmht-net-0/roaming3.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Dec 12 11:34:26 2024
- Last Check
- Thu Dec 12 21:02:24 2024
- Next Check
- Thu Dec 12 21:12:24 2024
- 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).
behmht.net/behmht-net-0/roaming3.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Thu Dec 12 11:34:58 2024
- Last Check
- Thu Dec 12 21:02:57 2024
- Next Check
- Thu Dec 12 21:12:56 2024
behmht.net/behmht-net-1/NRPS: roaming0.govroam.uk
(212.219.190.139) -
Unknown Client
/
Port 1812 Drop
/
Bad Client Shared Secret
/
Dropping Auth Requests
/
behmht.net/behmht-net-1/roaming0.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 14.82 ms
- Last State Change
- Thu Dec 12 11:33:53 2024
- Last Check
- Thu Dec 12 21:03:43 2024
- Next Check
- Thu Dec 12 21:13:43 2024
behmht.net/behmht-net-1/roaming0.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Dec 12 11:34:01 2024
- Last Check
- Thu Dec 12 21:03:59 2024
- Next Check
- Thu Dec 12 21:13:59 2024
behmht.net/behmht-net-1/roaming0.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Dec 12 11:31:59 2024
- Last Check
- Thu Dec 12 21:09:58 2024
- Next Check
- Thu Dec 12 21:19:57 2024
behmht.net/behmht-net-1/roaming0.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Dec 12 11:35:46 2024
- Last Check
- Thu Dec 12 21:03:44 2024
- Next Check
- Thu Dec 12 21:13:44 2024
- 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).
behmht.net/behmht-net-1/roaming0.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Thu Dec 12 11:33:02 2024
- Last Check
- Thu Dec 12 21:01:01 2024
- Next Check
- Thu Dec 12 21:11:01 2024
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
behmht.net/behmht-net-1/NRPS: roaming1.govroam.uk
(212.219.209.43) -
Unknown Client
/
Port 1812 Drop
/
Bad Client Shared Secret
/
Dropping Auth Requests
/
behmht.net/behmht-net-1/roaming1.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 13.32 ms
- Last State Change
- Thu Dec 12 11:34:42 2024
- Last Check
- Thu Dec 12 21:04:32 2024
- Next Check
- Thu Dec 12 21:14:32 2024
behmht.net/behmht-net-1/roaming1.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Dec 12 11:35:13 2024
- Last Check
- Thu Dec 12 21:05:12 2024
- Next Check
- Thu Dec 12 21:15:12 2024
behmht.net/behmht-net-1/roaming1.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Dec 12 11:37:13 2024
- Last Check
- Thu Dec 12 21:05:12 2024
- Next Check
- Thu Dec 12 21:15:11 2024
behmht.net/behmht-net-1/roaming1.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Dec 12 11:33:20 2024
- Last Check
- Thu Dec 12 21:01:19 2024
- Next Check
- Thu Dec 12 21:11:19 2024
- 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).
behmht.net/behmht-net-1/roaming1.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Thu Dec 12 11:33:55 2024
- Last Check
- Thu Dec 12 21:01:54 2024
- Next Check
- Thu Dec 12 21:11:54 2024
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
behmht.net/behmht-net-1/NRPS: roaming2.govroam.uk
(212.219.247.59) -
Unknown Client
/
Port 1812 Drop
/
Bad Client Shared Secret
/
Dropping Auth Requests
/
behmht.net/behmht-net-1/roaming2.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 20.63 ms
- Last State Change
- Thu Dec 12 11:35:16 2024
- Last Check
- Thu Dec 12 21:05:06 2024
- Next Check
- Thu Dec 12 21:15:06 2024
behmht.net/behmht-net-1/roaming2.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Dec 12 11:37:33 2024
- Last Check
- Thu Dec 12 21:07:32 2024
- Next Check
- Thu Dec 12 21:17:31 2024
behmht.net/behmht-net-1/roaming2.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Dec 12 11:34:12 2024
- Last Check
- Thu Dec 12 21:02:10 2024
- Next Check
- Thu Dec 12 21:12:10 2024
behmht.net/behmht-net-1/roaming2.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Dec 12 11:33:59 2024
- Last Check
- Thu Dec 12 21:01:56 2024
- Next Check
- Thu Dec 12 21:11:56 2024
- 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).
behmht.net/behmht-net-1/roaming2.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Thu Dec 12 11:33:15 2024
- Last Check
- Thu Dec 12 21:01:13 2024
- Next Check
- Thu Dec 12 21:11:11 2024
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
behmht.net/behmht-net-1/NRPS: roaming3.govroam.uk
(195.194.21.203) -
Unknown Client
/
Port 1812 Drop
/
Bad Client Shared Secret
/
Dropping Auth Requests
/
behmht.net/behmht-net-1/roaming3.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 20.34 ms
- Last State Change
- Thu Dec 12 11:35:37 2024
- Last Check
- Thu Dec 12 21:05:27 2024
- Next Check
- Thu Dec 12 21:15:27 2024
behmht.net/behmht-net-1/roaming3.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Thu Dec 12 11:36:09 2024
- Last Check
- Thu Dec 12 21:06:09 2024
- Next Check
- Thu Dec 12 21:16:08 2024
behmht.net/behmht-net-1/roaming3.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Thu Dec 12 11:36:17 2024
- Last Check
- Thu Dec 12 21:04:16 2024
- Next Check
- Thu Dec 12 21:14:16 2024
behmht.net/behmht-net-1/roaming3.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Thu Dec 12 11:35:53 2024
- Last Check
- Thu Dec 12 21:03:52 2024
- Next Check
- Thu Dec 12 21:13:52 2024
- 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).
behmht.net/behmht-net-1/roaming3.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Thu Dec 12 11:33:31 2024
- Last Check
- Thu Dec 12 21:01:29 2024
- Next Check
- Thu Dec 12 21:11:28 2024
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
Called Station ID Check
- Output
- WARNING: 100% Missing SSID, as of 2024-12-12 20:54:14. 100% MAC format wrong - should use a '-' to separate hex pairs (last: 2024-12-12 20:54:14)
- Last State Change
- Thu Dec 12 12:03:36 2024
- Last Check
- Thu Dec 12 20:58:35 2024
- Next Check
- Thu Dec 12 21:13:33 2024
- 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.
- Solution:
- Configure your wireless system to provide the CSI in the RFC3580 format.
Calling Station ID Check
- Output
- WARNING: 100% MAC format wrong, missing separator (last: 2024-12-12 20:49:45)
- Last State Change
- Thu Dec 12 12:01:36 2024
- Last Check
- Thu Dec 12 20:56:34 2024
- Next Check
- Thu Dec 12 21:11:34 2024
- 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
- WARNING: 100% Missing Operator-Name (last: 2024-12-12 20:54:14)
- Last State Change
- Thu Dec 12 12:01:55 2024
- Last Check
- Thu Dec 12 20:56:53 2024
- Next Check
- Thu Dec 12 21:11:52 2024
- Meaning:
- Operator-Name is missing from RADIUS requests. Operator-Name identifies the site sending the requests and is used by home sites in audit trails and in cases of mis-use.
- Solution:
- Where possible (FreeRADIUS, radsecproxy, RADIATOR) Operator-Name should be configured to send the site identifier (in the format 1realm.name e.g. 1holby.nhs.uk).
Realm Syntax Check
- Output
- WARNING: 63% 3GPP realm (last: 2024-12-12 20:54:14)
- Last State Change
- Thu Dec 12 12:04:39 2024
- Last Check
- Thu Dec 12 20:59:38 2024
- Next Check
- Thu Dec 12 21:14:37 2024
- Meaning:
- Users and devices often put in their email addresses or preconfigured setting such as '@gmail.com' or '3gppnetwork.org' which are never going to be Govroam realms.
- Solution:
- Filter out the common realms which are never going to be Govroam sites.
VLAN Check
- Output
- OK: 100% No VLAN attr present (last: 2024-12-12 20:59:50)
- Last State Change
- Thu Dec 12 12:03:55 2024
- Last Check
- Thu Dec 12 21:03:53 2024
- Next Check
- Thu Dec 12 21:18:52 2024