Re: Ascend -> Radius

Kevin Smith (kevin@ascend.com)
Mon, 28 Jul 1997 13:29:04 -0700

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: jtt: "DMS-100 switch"
Previous message: Zak Wolfinger: "RE: Log Parser for NT - Binary not Perl?"
In reply to: Tim Flavin: "How could this be?"

At 04:37 PM 7/27/97 -0700, Benjamin D. Hutchins wrote:
>> My Ascends - > Livingston Radius detail files
>> indicate Request-Authenticator = Unverified
>> This line does not show up on PM generated detail files.
>>
>> Issues? or not to worry.
>
>Looks like Ascend's RADIUS client doesn't sign its packets properly
>per the RFC yet. RADIUS 2.0 and 2.0.1 don't insist on it yet and log
>the above when an unsigned packet comes in. Eventually, as we move
>toward full RFC compliance (and the RFC moves toward non-draftness),
>we'll start refusing them.

The Ascend NAS code has always signed Accounting packets - even when the
PM didn't (despite it being in the then RADIUS spec.). You'll most
likely find that the auth keys have not been configured correctly on
the MAX....

Kevin

Next message: jtt: "DMS-100 switch"
Previous message: Zak Wolfinger: "RE: Log Parser for NT - Binary not Perl?"
In reply to: Tim Flavin: "How could this be?"