FreeRadius2 issue when deployed as proxy for EAP-TLS

Matthew Newton mcn4 at leicester.ac.uk
Tue Apr 14 14:05:22 CEST 2015


Hi,

On Tue, Apr 14, 2015 at 11:46:59AM +0000, Muhammad Faisal wrote:
> The dubug logs are pasted below for your kind review the issue
> seems " 14 Apr 2015 10:13:15,938 [ DEBUG ] AUTH-THR-8 [BASE AUTH
> DRIVER]: Request eligible for Basic authentication." due to
> which request is rejected by Home server:

Don't know what those logs are - maybe I should have been more
clear. We need the debug output from the FreeRADIUS server that
you get when running

  radiusd -X

so we can see what FreeRADIUS is doing. This is the FreeRADIUS
list...

Having said that this log line indicates that an EAP-Message with
EAP type EAP-TLS arrived. So whatever system this log comes from,
I'm guessing EAP-TLS isn't configured properly. It doesn't look
like a FreeRADIUS issue.

14 Apr 2015 11:15:25,901 [ INFO  ] AUTH-THR-8 [AUTHENTICATION SERVICE]: Received ACCESS_REQUEST from 192.168.52.71:1814 with ID:213 and Length:246 User-Name = 20107A2071EA at testbed.com NAS-IP-Address = 192.168.52.75 Calling-Station-Id = 20107a2071ea NAS-Identifier = HW-WASN Event-Timestamp = 1428991780 EAP-Message = 0x02a6001f01323031303741323037314541407175626565746573742e636f6d WiMAX WiMAX Capability Attribute =  WiMAX Release = 0x312e31  Accounting Capabilities = 2  Hotlining Capabilities = 1  Idle Mode Notification Capabilities = 1  WiMAX WiMAX Capability Attribute =  WiMAX Release = 0x15000060b52e0f003030303030373030313131301a0d0000  Framed-Interface-Id = 307:50:4600:3D

Please send plain text messages to the list not HTML. Whatever you
sent was really mangled up.

Matthew


-- 
Matthew Newton, Ph.D. <mcn4 at le.ac.uk>

Systems Specialist, Infrastructure Services,
I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom

For IT help contact helpdesk extn. 2253, <ithelp at le.ac.uk>


More information about the Freeradius-Users mailing list