Re: Ascend unknown code 33 entries
Radius1 from lucent is much older than the rfc ... On Fri, 2002-04-12 at 00:13, Artur Hecker wrote: just a detail :) I am having the same problem with unknown code 33 packets on a newly installed FreeRadius 0.5 server auth'ing some Ascend MAX 4000's. (I've been using Ascend-hacked RADIUS since '95 and figured it was time for a change..:-) ah that's pretty cool! because RADIUS (RFC 2058) officially exists since 01/97... wow! ;-) evil-artur -- artur[at]hecker.info - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Ascend unknown code 33 entries
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
Re: Ascend unknown code 33 entries
At 04:29 PM 11/04/2002 -0400, you wrote: Ron Grant [EMAIL PROTECTED] wrote: But I DO know what causes them - they're Session Timer packets - And not RFC standard... If I had my way, all of my ISDN and K56 customers would finally come to their senses and purchase our ADSL services. TAOS 7.0.28 release docs mention that ticket 4757 fixed a problem with the MAX unit sending Navis Access logging transmissions to radius accounting, so I'm going to try upgrading to see if it fixes the basic problem. I suppose I could write a script that would give me the answers I need after the fact - run through the syslog files and match usernames against classes... 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. Hmmm, couple things come to mind.might tinker and see what happens if above update doesn't solve things - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Ron Grant, RHCE (Red Hat Linux Certified Engineer) [EMAIL PROTECTED]or [EMAIL PROTECTED] Convergence Network Research Ltd. (604) 737-2113 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
