Alan DeKok wrote:
Frank Bollet wrote:
How could I define a specific accounting for a given realm ?
You don't.
So, the best practice here is to put specific accounting in
sites-available/default ?
For example:
### File: sites-available/default
[...]
accounting {
if (Realm == foo) {
On Wed, Oct 27, 2010 at 10:06:30AM +0100, Frank Bollet wrote:
Is there a way to separate the configuration for each partner, or should I
just
put everything in sites-available/default because it's how it's supposed to
work?
Hmm, isn't it possible to use $INCLUDE in there, too, so the
Frank Bollet wrote:
So, the best practice here is to put specific accounting in
sites-available/default ?
Isn't that what I already said?
I obviously misunderstood the virtual server purpose. I'm basically just
trying
to separate each realm (actually *partners*, who can have multiple
Alan DeKok wrote:
Yes, you can. But you then need to proxy (i.e. route) the packets to
the correct destination virtual server. You weren't doing that.
And how could I do that ?
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Frank Bollet wrote:
If I define home servers and a virtual server in a home server pool, the
virtual
server is only used for pre/post proxy. accounting {} is used from
sites-enabled/default.
Yes. That's the way it works.
How could I define a specific accounting for a given realm ?
5 matches
Mail list logo
