22 Apr
2008
22 Apr
'08
10:41 a.m.
Ryan wrote:
I have worked around it using the proxy-inner-tunnel method to terminal the EAP on the front radius and then proxy MS-CHAP to an internal radius that will do an LDAP bind with an additional attribute.
Ok...
As the front radius will also handle EAP requests that will not be handled by the internal radius, will it just proxy the EAP request based on the domain or it will terminate and forward to my internal radius instead?
Huh? You said in the first paragraph that it will terminate & forward. Where's the confusion? Alan DeKok.