<[EMAIL PROTECTED]> wrote: > Question 1. RFC 3579 states that "EAP-Start is indicated by sending an > EAP-Message attribute with a length of 2 (no data). I interpret this to > be the following two bytes '0x49 0x02'.
Hmm... I think that's a typo, or, at least, it's not the way most clients work. > But when I send a packet > containing such an attribute to freeradius it does not see it as an EAP > start. > Below is the packet that was sent to free radius ... > rad_recv: Access-Request packet from host 10.230.199.211:33118, id=1, > length=92 > User-Name = "DNIS:123456789" > NAS-IP-Address = 1.2.3.4 > Service-Type = Call-Check > Called-Station-Id = "0123456789" > Calling-Station-Id = "0123456789" > EAP-Message = 0x Which is an empty EAP message. It appears to satisfy the RFC's, but I don't think any client behaves that way. Most EAP clients use a two-byte EAP packet, which means a RADIUS EAP-Message of length 4. > To get around this I send the EAP-Message > 0x4f 0x0c 0x01 0xff > > rlm_eap: EAP packet type identity id 255 length 0 > rlm_eap: Got EAP_START message > modcall[authorize]: module "eap" returns handled > > Am I reading the RFC wrong? I don't think so, but in ~2 years of using the EAP module, this has never come up before. > I send the following EAP-Message > Radius-Attribute = 0x 4f 0c 02 ff 00 0a 01 68 65 6c 6c 6f > This is a EAP-Message with code=Response and Type = Identity, = > however > the debug states that the type is=20 > notification. What am I doing wrong? Nothing. Use the latest CVS snapshot. 0.9.0 is *very* old. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
