Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Ascend radiusd and USR TCR - radius accounting
At 10:27 AM 2/11/98 +0000, Alex Bligh wrote:
>Kevin,
>
>> Do you know for sure that the TC sends the authenticator in it's
>> accounting packets.....?
>
>I haven't dumped the packets out bit by bit - if you remove the
>check that the MD5 results are the same, it all comes through OK.
>So either it's not filling in the authenticator (doubtful I'd
>have thought as the same thing happens on old USR s/w as the
>newest of the new s/w on their Hyperxxx platform), or Ascend
>and USR use a different method to calculate the authenticator.
Since the USR code is based on Livingston ComOS, I would have assumed
their RADIUS/Accounting was also. I know that the first releases of
Livingston RADIUS *did not* include the authenticator in authentication
packets (accounting was still not done at that time), so we had some
problems when they were using Ascend's RADIUS daemon which required
it.
I'll check with our RADIUS guru to see if this is a known issue.
Kevin
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
References: