Alexander Serkin <[EMAIL PROTECTED]> wrote:
> I did not think radiusd rewrites unix timestamp into date.
> Just because previous radius i was using used to put the timestamp into 
> accounting as an integer.

  Which I, for one, have a hard time understanding.

> Does it mean that %S takes the timestamp from the Event-Timestamp
> field of the accounting packet?

  No.  It takes the time that the packet was received.  The
Event-Timestamp attribute MAY be a lie.

> Hm. That's not a trick. And not good at all. %S takes time at which the 
> request comes to radius.

  Exactly.  You can't trust the NAS.

> I've pushed a pack of accounting records to the radius with radrelay. 
> When using %S i have a session as this one:
> 
> id: D4776040004F9475 start - 18-MAY-05 12.25.15, stop - 18-MAY-05 12.25.15
> 
> and actual values are:
> 
> id: D4776040004F9475 start: 18/05/2005 12:03:46, stop: 18/05/2005 12:07:34
> 
> does not seem like a valid "relay".

  Since you're not going to explain why, I'm guessing it's not really
a problem.

> Now who can give me a hint of pushing Event-Timestamp like "May 18 2005 
> 12:08:18 MSD" into oracle TIMESTAMP WITH TIME ZONE field?

  Edit oraclesql.conf to use the query you want.  That's why the
queries are configurable.

  Alan DeKok.

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to