Ok. RFC says exactly that "The Value field is four octets encoding an unsigned integer with the number of seconds since January 1, 1970 00:00 UTC."
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.
Moreover i did not notice this helpful trick in variables.txt:
" %S request timestamp in SQL format"
Does it mean that %S takes the timestamp from the Event-Timestamp field of the accounting packet?
Hm. That's not a trick. And not good at all. %S takes time at which the request comes to radius.
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".
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?
-- Alexander
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
