You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How to fix:
Comment or remove this parameter and enjoy correct statistic.
Log output from the FreeRADIUS daemon
Ready to process requests
(2) Received Status-Server Id 234 from 127.0.0.1:56590 to 127.0.0.1:18121 length 74
(2) Message-Authenticator = 0xa5c4b7c1ab2d8624705f6b033e431cd0
(2) FreeRADIUS-Stats-Server-IP-Address = 10.16.20.230
(2) FreeRADIUS-Stats-Server-Port = 1812
(2) FreeRADIUS-Statistics-Type = 131
(2) # Executing group from file /etc/raddb/sites-enabled/status
(2) Autz-Type Status-Server {
(2) [ok] = ok
(2) } # Autz-Type Status-Server = ok
(2) Sent Access-Accept Id 234 from 127.0.0.1:18121 to 127.0.0.1:56590 length 0
(2) FreeRADIUS-Stats-Error = "Failed to find home server IP"
(2) Finished request
Relevant log output from client utilities
cat <<EOF | radclient -x localhost:18121 status adminsecret
Message-Authenticator=0x00
FreeRADIUS-Stats-Server-IP-Address = 10.16.20.230
FreeRADIUS-Stats-Server-Port = 1812
FreeRADIUS-Statistics-Type = 0x83
EOF
Sent Status-Server Id 234 from 0.0.0.0:56590 to 127.0.0.1:18121 length 74
Message-Authenticator = 0x00
FreeRADIUS-Stats-Server-IP-Address = 10.16.20.230
FreeRADIUS-Stats-Server-Port = 1812
FreeRADIUS-Statistics-Type = 131
Received Access-Accept Id 234 from 127.0.0.1:18121 to 127.0.0.1:56590 length 57
FreeRADIUS-Stats-Error = "Failed to find home server IP"
Backtrace from LLDB or GDB
No response
The text was updated successfully, but these errors were encountered:
What type of defect/bug is this?
Unexpected behaviour (obvious or verified by project member)
How can the issue be reproduced?
src_ipaddr
into anyhome_server
instance in the proxy.conf file. For exmple:How to fix:
Comment or remove this parameter and enjoy correct statistic.
Log output from the FreeRADIUS daemon
Relevant log output from client utilities
Backtrace from LLDB or GDB
No response
The text was updated successfully, but these errors were encountered: