Alan DeKok wrote:

Joe Maimon <jmaimon@ttec.com> wrote:

...

But if I wanted to I could already send back specific attr's based on client IP address. Abstracting it to a configured commonality, such as a substring in shortname makes for a very simple setup.

The feature I detailed lets you do that. The only problem is that the "users" file isn't designed to implement such complex functionality.

In the CVS head, the "policy" module DOES support more complex functionality.

...

and in my users file I would have

DEFAULT Client-Short-Name =~ "dialupresllerX.*" <LT2P tunneling attributes for example>

You can apply the string expansion I described above to create that attribute. e.g. Add "Client-Short-Name" to the dictionary, and in the "hints file, do:

DEFAULT Client-Short-Name = "%{config:....."}

You can then do the checks you want in the "users" file.

This is cool and all but the limitation imposed by requiring clients IP addresses is a pain. Should/Could this be addressed? Would a patch be welcomed? Has it already been addressed?