There may be some confusion, I am currently logging auth and accounting information in seperate folders that are labeled by client ip addresses, but those are the detail auth logs, I am working with just the radius.log file. Below is a sample of what I get in the radius log file, notice the from client
207.32.194.0/23 is the subnet which is in the clients.conf file also attached below. So rather than manually entering all my router ips is there a shorter way to edit the way the radius.log file is built?
*SAMPLE from Radius.log
Fri Jun 3 12:39:17 2011 : Auth: Login incorrect: [00:60:B3:3C:A2:3C/] (from cli
ent
207.32.194.0/23 port 2207252597)
*SAMPLE from clients.conf file
I did browse thru some of the previous posts but never really saw any answers... I have a feeling I will need to do what the clients.conf file recommends and that is to manually enter each one of my routers :( a script would be nice to do that but I am not very educated in scripting etc... thanks for any additional help!
Jason Frawley
208-740-3290
On Fri, Jun 3, 2011 at 12:31 PM, Fajar A. Nugraha
<list@fajar.net> wrote:
On Sat, Jun 4, 2011 at 2:19 AM, Jason Frawley <
jfrawley81@gmail.com> wrote:
> Sorry I meant to say log the client ip and not the subnet in which its in
> ....eg. log shows request from
207.32.194.0/23 but I need it to show the
> actual ip in which the request came from. Eg. 207.32.194.4
archive if you're interested in the complete responses.
Basically you can either:
- ADD what information logged (look at radiusd.conf, look for msg)
- log to a NEW file, with another format altogether (see linelog module)
Whichever path you choose, looks like you can use NAS-IP-Address or
Client-IP-Address attribute as the extra information.
--
Fajar