Hi all,
I have a question about the debugging of EAP conversations (while
trying to set up an auth chain using PEAP)
e.g. freeradius -X gives me:
rad_recv: Access-Request packet from host 192.168.3.246:21645, id=1, length=134
User-Name = "testuser"
Framed-MTU = 1400
Called-Station-Id = "000d.295f.8f7d"
Calling-Station-Id = "000d.2911.9aea"
Service-Type = Login-User
Message-Authenticator = 0x99e2968efa6c8dc3db51f29cc1696135
EAP-Message = 0x0202000d017465737475736572
NAS-Port-Type = Wireless-802.11
NAS-Port = 2
NAS-IP-Address = 192.168.3.246
NAS-Identifier = "warz001"
Processing the authorize section of radiusd.conf
modcall: entering group authorize for request 0
modcall[authorize]: module "preprocess" returns ok for request 0
modcall[authorize]: module "mschap" returns noop for request 0
rlm_realm: No '@' in User-Name = "testuser", looking up realm NULL
rlm_realm: No such realm "NULL"
modcall[authorize]: module "suffix" returns noop for request 0
rlm_eap: EAP packet type response id 2 length 13
rlm_eap: No EAP Start, assuming it's an on-going EAP conversation
Now take the EAP-Message:
0x 02 02 000d 01 74 65 73 74 75 73 65 72
hex code id length data (9 octets)
Splitting done right? If so, code, id, and length are consistent with
rlm_eap: EAP packet type response id 2 length 13
But why are there only 9 bytes of data -- I expect 13?
Is it truncated in some way?
Thanks, Martin
--
Dr. Martin Pauly Fax: 49-6421-28-26994
HRZ Univ. Marburg Phone: 49-6421-28-23527
Hans-Meerwein-Str. E-Mail: [EMAIL PROTECTED]
D-35032 Marburg
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
