This is normal radius protocol behaviour, as the remote radius server does not usually return a reason in the reject.
You could configure the remote end to send a Reply-Message with the reject reason and then write a hook in the HQ radiator to log the Reply-Message, but I can't think of any other way to do what you describe.
regards
Hugh
On Thursday, August 22, 2002, at 05:34 AM, Le Anh Tuan wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I configured a roaming system between our HQ and Branch office in seperate location using Radiator and <AuthBy Radius>. But I can not get a reason message each time a authentication reject occur, AuthBy Radius only returns message like 'INFO: Access rejected for user: Proxied' or 'INFO: Access rejected for user:'. Can you help me how to configure Radiator to get a reason message, I need it to put into my <AuthLog SQL> to help my administration work.
Thank you very much.
Le Anh Tuan
R&D Department
Netnam Corporation
Institute of Information Technology
Email: [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4
iQA/AwUBPWRb1BLw+KcRUiRLEQJWKgCgrD80FhdzABN9e+etScPsJS3qom0AnRdy
DZvo2KmUrDFUOMWRkRntMR5q
=ILzK
-----END PGP SIGNATURE-----
NB: I am travelling this week, so there may be delays in our correspondence.
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
