However, it _might_ be very powerful and work with some sort of templating or aliasing feature. This is completely off the top of my head, but maybe something like
radius.conf:
aliases { "select-auth-type" = "receive Access-Request" "authenticate-user" = "process Access-Request" "authorize-user" = "send Access-Accept" "process-failure" = "send Acecss-Reject" ... }
This might actually be very nice, especially in the transition
post-proxy (Post-Proxy-Type Fail) and post-auth (Post-Auth-Type Fail) are already messy IMO, so this might help sort them out.
They could be mapped as above perhaps? :-) Stefan Paetow Moonshot Industry & Research Liaison Coordinator t: +44 (0)1235 822 125 gpg: 0x3FCE5142 xmpp: stefanp@jabber.dev.ja.net skype: stefan.paetow.janet jisc.ac.uk Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc¹s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800. Jisc Collections and Janet Ltd. is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under Company No. number 2881024, VAT No. GB 197 0632 86. The registered office is: Lumen House, Library Avenue, Harwell, Didcot, Oxfordshire, OX11 0SG. T 01235 822200.