Cool!
> Now radius (merit 2.4.20) won't stay up for more than a few minutes..
Shit!
> It core dumps with this:
>
> get_radrequest: Request from cc784e09 (ts21.ais.net[1026]) code = 4, id =
> 52, le
> n = 94
> Acct-Session-Id = "00000006"
> User-Name = "whitting"
> NAS-IP-Address = "204.120.78.9"
> NAS-Port = 7
> Received unknown attribute 61
> of length 4: 0x00000000
> Acct-Status-Type = Start
> Acct-Authentic = RADIUS
> Service-Type = Framed
> Framed-Protocol = PPP
> Framed-IP-Address = "206.225.198.6"
> Received unknown attribute 128
> of length 242:
> 0x0800C0F40706000000010806CEE1C00F0000000000000000000000000000000
> 00000000000000000000000000000000000000000000000000000000000000000000000000000000
> 00000000000000000000000000000000000000000000000000000000000000000000000000000000
> 0000000000000000000000000000000000000
> ^C
> [1] + Segmentation fault ./radiusd -p 1645 -q 1646 -x -z (core
> dumped)
Well, the good news is that version 2.4.20 produced a core file. (One
of us here was not sure the server code still retained that ability...)
I find it hard to understand that if you're running 2.4.20 why it
doesn't recognize attribute 61 (NAS-Port-Type) since that is clearly
legal AND in the dictionary. Did you install the 2.4.20 dictionary
when you installed the 2.4.20 version server?
The attribute 128 completely baffles me -- maybe it is a Livingston
mole! (just kidding, guys) :-)
I've never heard of it and it isn't in the DRAFT RADIUS RFCs as far
as I know...
Even so, an unknow attribute should not dump core, it should be logged
and ignored. Did you make any source changes or patches to 2.4.20?
Regards,
web...
-- William Bulley, N8NXN Senior Systems Research Programmer Merit Network Inc. Domain: web@merit.edu 4251 Plymouth Road MaBell: (313) 764-9993 Ann Arbor, Michigan 48105-2785 Fax: (313) 747-3185