On 01/15/2013 02:36 AM, David Zych wrote: > I'm trying to rework my Radiator configuration to use multiple instances > as suggested e.g. in > http://www.open.com.au/pipermail/radiator/2012-November/018728.html. > > In the event of an Access-Reject, I would like for the front-end > server's reason string (i.e. %1 in FailureFormat) to reflect the true > reason provided by the back-end instance in the Reply-Message attribute,
Hello David, please see patches for 4.11. The contents of Reply-Message from upstream is now available if it is present. 'Proxied' is not forced as the reason anymore. Please let us know if this does what you were expecting. Thanks, Heikki -- Heikki Vatiainen <h...@open.com.au> Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
