 |  |
Graeme Easton wrote:
Re: radius file importing
From: Shawn Hogan
Date: Tuesday, June 23, 1998
Time: 7:50:20 pm
>Am I the only one that has trouble importing RADIUS log files? Sean was
>kind enough to redo the parser.usr utility for me, but I'm still not
>having any luck. I'm using Livingston Radius for NT, and have attached a
>sample detail file. Its currently cutting off the first letter of the
>username, since my radius doesnt put a "P" in front of the name....it
>also imports the wrong attribute for time online. I tried moving the
>fields when importing with parser.usr, but the fields are in a different
>order depending on weather its a "start" record or a "stop" record.
>
>Also, it would be nice to be able to strip the <CR><TAB> automatically
>with a batch file. Does anyone know of a dos command line utility that
>will do this?
>
>Please help while I still have a little hair left <BG>
Well, I took a look at your log file, and it looks a little strange to
me. By looking at the stop record, you cannot tell the amount of time
the session was active. Instead, it uses (or at least appears to) a
timestamp. That *probably* needs to be compared to the start record to
get an accurate amount of time online.
What it LOOKS like to me is that if you took the stop record timestamp
and subtracted the start record timestamp, that would be the number of
seconds that session lasted.
The Parser utility isn't going to work for you, because it assumes that
the seconds online is stored in the stop record, and therefore totally
ignores the start record.
This is kind of the reason that Optigold ISP doesn't import the log files
directly. There are many different flavors of RADIUS log files, and
there are too many to try to support them all. So instead, I made the
parser which will parse the most popular ones. But, if you have a
different style, it's going to be pretty much up to you to parse the log
file.
So to answer your question, it's not something you are doing wrong, and
it's not something wrong with parser either. It has to do with the fact
that your log files are "non-standard" (if there is such a thing as a
standard log file).
- Shawn
-------------------------------
Shawn D. Hogan
President, Data Point Solutions
http://www.data-point.com
(619) 452-3696
ICQ: 8319647
Messages In This Thread:
Return to Digital Point Solutions' Home Page