30 likes | 210 Views
EAP /EAP-Method interface. EAP Method. EAP Method. Method-state. Method-state. Startmethod rx.Rsp Rx.NAK. rdy.Req rdy.noReq. rxMethodReq. rdy.Rsp rdy.noRsp. EAP Layer. EAP Layer. 802.1x. 802.1x. CHALLENGE bldReq Methodstate= CON rdy.Req=TRUE. PassThru Method. startMethod.
E N D
EAP /EAP-Method interface EAP Method EAP Method Method-state Method-state Startmethod rx.Rsp Rx.NAK rdy.Req rdy.noReq rxMethodReq rdy.Rsp rdy.noRsp EAP Layer EAP Layer 802.1x 802.1x
CHALLENGE bldReq Methodstate= CON rdy.Req=TRUE PassThru Method startMethod Initialize Method eapmsg=null UCT TIMEOUT increment timeout UCT RADIUS- Request bldRADReq(eapmsg) send RADIUS Request radWhile=<timeout> radWhile=0 rcvRad.challeenge rcvRad.reject rcvRad.accept rxResp!!rxNAK REJECT bldReq MethodState=Fail rdyReq=TRUE ACCEPT bldReq methodState=SUC rdyReq=TRUE UCT UCT Done
passthru method questions • A number of special cases seem to appear • current eap assumes method does not deal with NAK - but need to for forwarding to RADIUS • current eap assumes method does not send Success/Fail - but need to with passthru • Integrity Check interface could be added if local integrity checking is done • e.g. in RADIUS-Request include an integrityCheck function and a ICFail state that to transition to if the check fails • My Conclusion -- pass thru method is not quite right, probably need a passthru “gateway” which translates between requirements for eap transport.