[rbak-nsp] npm proxy radius problem

[Frans Legdeur]

Hi,

Use debug aaa radius and debug aaa rad-attr in combination with debug aaa
author and debug aaa authen.
This should spit out the full details for your subscriber.

Timeout might be the result that the radius server is not able to
authenticate your subscriber.
It might not respond due to the proxy no responding to the originating NPM.

Can you look at the log file on the NPM? Provide it in debug state?
Did you try to test the accounting with the same command?
Ie. Test aaa accounting username bla at bla protocol radius and what is the
result?

The shared key¹s must be equal between NPM and configured radius server at
the SmartEdge.

Just a few hinds to look at, the packet sanity check is not familiar to me.

Regards,

Frans.



From: burgerkill <burgerkill at gmail.com>
Date: Thu, 3 Feb 2011 00:50:59 +0700
To: <redback-nsp at puck.nether.net>
Subject: [rbak-nsp] npm proxy radius problem

Hi,

Need a bit help here, i have NPM server that configured as radius proxy.I
have check on BRAS using sh rad servers both stats on authentication and
accounting are alive.But when am did test aaa authentication username
usertest at domain password test protocol radius ,the result was timeout.

I do some debugging command using debug aaa authen and it said failed on
packet sanity check.Is there something missing config on BRAS or NPM ?

Many thanks for help

Regards,
Burgerkill




_______________________________________________
redback-nsp mailing list
redback-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/redback-nsp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20110202/ea08167f/attachment.html>