Ron Grant <[EMAIL PROTECTED]> wrote: > But I DO know what causes them - they're "Session Timer" packets -
And not RFC standard... > Well, (33 > 11) is true, so..... I'm off to find out if Ascend > changed the packet code for Session-Timer packets from 33 to > something rational before being gobbled up by Lucent. If not, then I > might be looking for some help in adding "code 33" handling to > radiusd.c (maybe with an "ASCEND_SESSIONTIMER_HACK" flag). Hmm... I would rather try something else. > Or is there some really simple way to add a custom packet type that > I haven't found yet? No. That requires some server modifications. I still don't understand why Ascend couldn't send an accounting packet with a fake user name. That would have done the same thing, and would be MUCH easier to handle. Alan Dekok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
