Closed nchaigne closed 10 years ago
The simple virtual server configuration I used:
#
# this is a very simple virtual server to test proxy of EAP requests.
#
# configuration items
SRS_3gpp_fictive_realm = 3gpp.test
server server-proxy {
listen {
type = auth
ipaddr = *
port = 1812
}
authorize {
# Handle EAP Authentication request
if (EAP-Message) {
update control {
&Proxy-To-Realm := ${SRS_3gpp_fictive_realm}
}
}
}
pre-proxy {
}
post-proxy {
Post-Proxy-Type Fail {
update {
reply:Reply-Message := "no response from home server"
}
}
}
}
Thanks for the fix! I've got a question though to be sure this is what you intended: Previously, a request with no response from home server went through "Post-Proxy-Type Fail", then "Post-Auth-Type REJECT", then a Reject reply was sent back to client.
Now the request goes through "Post-Proxy-Type Fail", but not through "Post-Auth-Type REJECT", and no reply is sent back to client.
Is that the expected behaviour ?
No, that's not the correct behaviour. It should go through Post-Proxy-Type Fail, Post-Auth-Type Reject, then send a reject back.
Thanks, all seem ok this time :)
(follows https://github.com/FreeRADIUS/freeradius-server/issues/656)
Client sends one request (no reemissions) to FreeRADIUS, which proxies to home server. Home server does not respond.
The request is proxied 3 times to the home server. No reply is sent back to client.
Here is the full debug output, with "DEBUG_STATE_MACHINE" enabled: