Hi,
> > Of course ! But to simplify documentation, I've put all in one file
> > radiusd.conf except sql requests / config
>
> That's a terrible idea.
I was going to say the same thing. the old old server used to use a single
file for config...that
was actually a nasty thing. it now calls seperate modules....which all have
nice notes/comments
in them already. redacting that to a single flat file is horrible....even
worse, it makes looking
at the difference between your server config and the next release available
config - eg new options
etc almost impossible.
> > NAS-IP-Address = 127.1.1.1
> > F5-Acct = "Oct 18 17:18:59 local/lb2b notice mcpd[4820]:
> > 01070417:5: AUDIT - user radtest - transaction #40213784-2 - object 0 -
> > modify { pool_member { pool_member_pool_name \"......
> > WARNING: Empty section. Using default return values.
> > +- entering group accounting {...}
> > Invalid Accounting Packet
rlm_perl prints that out if there is no "Acct-Status-Type" attribute in the
packet - ie
its not really a nice valid accounting packet. this looks like auditing packets
being sent...
they might need to fix their code?
> > And one more question, can I replace it dynamically with, for example,
> > rlm_perl using the IP address from sender host (here 10.10.10.12 ?).
replace what? the NAS-IP-Address? yes - you can swap it with eg the
Packet-Src-IP-Address
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
