Freeradius没有收到任何请求
我配置了Freeradius使用MySQL,直到一段时间前,一切都在工作,当时一些队友抱怨他们无法对服务器进行身份验证。
因此,我在调试模式下再次启动了Freeradius,然后尝试了radtest测试密码127.0.0.0.1 0 Testing123
经典测试,但是我收到in ID 241套接字3
no Reply 。
实际上,似乎服务器没有收到任何东西,因为在日志中,我可以看到在运行radtest时可以看到可以处理请求消息。
从调试模式的输出来看,似乎自由半径正在侦听
radiusd: #### Opening IP addresses and Ports ####
listen {
type = "auth"
ipaddr = *
port = 1813
limit {
max_connections = 16
lifetime = 0
idle_timeout = 30
}
}
listen {
type = "acct"
ipaddr = *
port = 1814
limit {
max_connections = 16
lifetime = 0
idle_timeout = 30
}
}
listen {
type = "auth"
ipv6addr = ::
port = 1813
limit {
max_connections = 16
lifetime = 0
idle_timeout = 30
}
}
listen {
type = "acct"
ipv6addr = ::
port = 1814
limit {
max_connections = 16
lifetime = 0
idle_timeout = 30
}
}
listen {
type = "auth"
ipaddr = 127.0.0.1
port = 18120
}
Listening on auth address * port 1813 bound to server default
Listening on acct address * port 1814 bound to server default
Listening on auth address :: port 1813 bound to server default
Listening on acct address :: port 1814 bound to server default
Listening on auth address 127.0.0.1 port 18120 bound to server inner-tunnel
Listening on proxy address * port 36889
Listening on proxy address :: port 48860
,并且客户端配置对我来说似乎是正确的,
client localhost {
ipaddr = 127.0.0.1
proto = *
secret = testing123
# shortname = localhost
nas_type = other # localhost isn't usually a NAS...
limit {
max_connections = 16
lifetime = 0
idle_timeout = 30
}
}
您可以帮助我调试为什么它不再起作用吗?
I configured FreeRadius to use MySQL and everything was working until a while ago, when some teammates complained they cannot authenticate to the server.
So I started FreeRadius again in debug mode and I tried with the radtest testing password 127.0.0.1 0 testing123
classic testing, but I receive No reply from server for ID 241 socket 3
.
Actually it seems that the server doesn't receive anything since in the log I just can see Ready to process requests message, when I run the radtest.
From the output of the debug mode, it seems Free Radius is listening
radiusd: #### Opening IP addresses and Ports ####
listen {
type = "auth"
ipaddr = *
port = 1813
limit {
max_connections = 16
lifetime = 0
idle_timeout = 30
}
}
listen {
type = "acct"
ipaddr = *
port = 1814
limit {
max_connections = 16
lifetime = 0
idle_timeout = 30
}
}
listen {
type = "auth"
ipv6addr = ::
port = 1813
limit {
max_connections = 16
lifetime = 0
idle_timeout = 30
}
}
listen {
type = "acct"
ipv6addr = ::
port = 1814
limit {
max_connections = 16
lifetime = 0
idle_timeout = 30
}
}
listen {
type = "auth"
ipaddr = 127.0.0.1
port = 18120
}
Listening on auth address * port 1813 bound to server default
Listening on acct address * port 1814 bound to server default
Listening on auth address :: port 1813 bound to server default
Listening on acct address :: port 1814 bound to server default
Listening on auth address 127.0.0.1 port 18120 bound to server inner-tunnel
Listening on proxy address * port 36889
Listening on proxy address :: port 48860
and also the client configuration seems correct to me
client localhost {
ipaddr = 127.0.0.1
proto = *
secret = testing123
# shortname = localhost
nas_type = other # localhost isn't usually a NAS...
limit {
max_connections = 16
lifetime = 0
idle_timeout = 30
}
}
Can you help me to debug why it doesn't work anymore?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
您已经更改了配置中的端口。 Auth应该在1812年的港口,而ACCT在1813年,而不是您目前的1813年和1814年。
You have changed the ports in the configuration. Auth should be on port 1812, and acct on 1813, not 1813 and 1814 as you currently have.