Correct login in TLS tunnel, but rejected

Alan DeKok aland at deployingradius.com
Tue Sep 2 14:03:27 CEST 2014


Thomas Hermarij Maimann Andersen wrote:
> However when they login we get the following in the radius log
> Sep  2 11:34:41 server radiusd[20048]: Login OK: [xuser/<via Auth-Type = EAP>] (from client aerohive-net port 0 via TLS tunnel)
> Sep  2 11:34:41 server radiusd[20048]: Login OK: [xuser/<via Auth-Type = EAP>] (from client aerohive-net port 0 via TLS tunnel)
> Sep  2 11:34:41 server radiusd[20048]: Login incorrect: [xuser/<via Auth-Type = EAP>] (from client aerohive-net port 0 cli 90-48-9A-69-XX-XX)
> Sep  2 11:34:41 server radiusd[20048]: Login incorrect: [xuser/<via Auth-Type = EAP>] (from client aerohive-net port 0 cli 90-48-9A-69-XX-XX)
> 
> The same user, on the same radio, on a different computer can login fine. So I am sure it’s a problem with the computer setup.
> 
> Can anyone explain to me what the difference is and possibly why it would fail?

  Run the server in debugging mode to see what's going on.  Nothing else
will give you the information you need.

  Alan DeKok.


More information about the Freeradius-Users mailing list