NAS-port-type doesn’t really help as I could have multiple port types over the bba-group.
Already going option 2, but it’s becoming un-maintainable with hundreds of intfs, even using regex matching… Also when moving/adding/removing ports from the router, I want to avoid having to alter the RADIUS server each time. I was hoping there was something, allowing to send something specific to each bba-group; or even per virtual-template since I can specify a different virtual-template per bba-group. -- inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP: https://inoc.net/~rblayzor/ > On Nov 13, 2017, at 7:55 PM, Guy Lowe <[email protected]> wrote: > > Either "radius attribute nas-port-type" to override NAS-Port-Type on the > interface, or maintain an interface->group mapping on the RADIUS server > side for use with NAS-Port. You'll need to preprocess the request to get > a usable string in either case. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
