Is there a paper somewhere which discusses EAP PEAP Challenges? I'm debugging a
new controller's access to radiator and finding that a working auth requires 11
udp packets each way and I don't understand why. What info is being passed?
---
Roberto Ullfig - rull...@uic.edu
ACCC Research Programme
Are all the challenges independent of each other? I can't find anything in the
debug log that ties the incoming packets together.
---
Roberto Ullfig - rull...@uic.edu
ACCC Research Programmer
From: radiator-boun...@open.com.au [mailto:radiator-boun...@open.com.au] On
Behalf Of Ullfig, Roberto A
Also, what does this mean?
Mon Apr 11 10:32:06 2016: DEBUG: Handling with EAP: code 2, 2, 12, 1
Mon Apr 11 10:32:06 2016: DEBUG: Response type 1
Mon Apr 11 10:32:06 2016: DEBUG: EAP result: 3, EAP PEAP Challenge
---
Roberto Ullfig - rull...@uic.edu
ACCC Research Programmer
From: radiator-boun...
Hi,
>Is there a paper somewhere which discusses EAP PEAP Challenges? I'm
>debugging a new controller's access to radiator and finding that a working
>auth requires 11 udp packets each way and I don't understand why. What
>info is being passed?
documented in the RFC and on resource
Hi,
>Are all the challenges independent of each other? I can't find anything in
>the debug log that ties the incoming packets together.
all seperate UDP packets - but with a known state - the RADIUS
server recognises the conversation (up to 256 from each NAS usually)
with latest patch
Hello Roberto -
Welcome to the wonderful world of EAP.
Note that EAP is essentially a stateful encrypted TCP tunnel, over RADIUS, over
UDP, hence the large number of packets back and forth for a single
authentication.
I wonder what substance they were abusing?
regards
Hugh
> On 12 Apr 201
