Jyoti Chatterjee wrote:
Actually, the requirement states that if the remote proxy server should authenticate all associate requests when it is up. When the remote proxy server is down only then the authentication can be done locally with the information cached from a previous successful request.
EAP doesn't work that way. Your requirement is impossible to implement.
I might be able to perform local authentication for an EAP-PEAP request coming from the client using self-signed certificates. Do you agree?
No.
Is there a specific configuration that you are talking about? I was never able to capture "status-server" packets using a tool like ethereal.
Did I say to use ethereal? No. I said to read proxy.conf. Did you do that? No. Why? If you're not interested in getting help on this list, don't ask questions here. Alan DeKok.