Other than the comments in radiusd.conf and 'man 5 regex' none.
That's too bad. Perhaps before 1.0, an effort can be made to improve the documentation somewhat? No use coding something esoteric, is there?
> 1. We use "[EMAIL PROTECTED]". If the realm is missing, we will use > attr_write to add it.
proxy.conf:
realm NULL{ [...]
Just so I'm clear on this, let me word my question another way:
In order to ensure that a realm is added to the packet from a particular NAS, you suggest I use the proxy.conf NULL function? This seems to go against your advice to another earlier this summer:
http://lists.cistron.nl/archives/freeradius-users/2003/07/msg01290.html
If not, where should I place the "autztype Rewrite { ...." function you describe? radiusd.conf? Where specifically?
> 2. Since we're AAA'ing using a SQL database, the username needs to be > parsed so that the username and the realm/domain is split. Then those, > plus the password, are checked against the SQL DB.
This is done automatically by the realm module.
Again, just so I'm sure I've properly communicated what I want to do, here is the situation reworded:
I want to ensure that only clients allowed to use a specific NAS are using it. Everyone else is rejected. Can the realm pass on the info needed to make the SQL call? Or should can I assign (for instance) a NAS to a particular group instead?
Thanks for you patience,
-- Stephen
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
