Dave Mason <[EMAIL PROTECTED]> wrote:
> Just so I'm on the right page, I assume I should do the patch and submit
> it in the usual way?
Yes. Also putting it on bugs.freeradius.org would help.
> If so, I'll clarify my understanding of what needs to happen. In
> eap.c/eap_start, I can return
Just so I'm on the right page, I assume I should do the patch and submit
it in the usual way?
If so, I'll clarify my understanding of what needs to happen. In
eap.c/eap_start, I can return EAP_OK instead of EAP_NOOP for the proxy
case. I dont see any other cases where EAP_OK is returned now.
Dave Mason <[EMAIL PROTECTED]> wrote:
> Along the way, I noticed that in the 1.0 server code, rlm_eap returns
> NOOP both for Access-Requests with an EAP-Message to be proxied and for
> Access-Requests with no EAP at all. It would be useful for me to write
> a configurable failover block in the
Hi,
I found the answer in auth.c near the beginning of rad_authenticate.
The trick is to return RLM_MODULE_HANDLED if the proxy reply is an
Access-Challenge.
Along the way, I noticed that in the 1.0 server code, rlm_eap returns
NOOP both for Access-Requests with an EAP-Message to be proxied an
Hi,
I'm using an old Freeradius server, v0.8.1, to proxy Access-Requests
with EAP-Messages. The outbound proxy works fine, but the proxy
response is getting mangled. The 1.0 server works fine, and I know the
real solution is to pick it up, but with my current deadline I cant port
the rest of
5 matches
Mail list logo
