Freeradius + MySQL wrong Timestamps

[Alan DeKok]

Satish Patel wrote:
> If you check log sip sending stop packet but and freeradius able to update start accounting but not stop. 

  Because the NAS is broken.

Tue Aug 12 22:46:20 2014 : Info: [sql]  expand: stop packet with zero
session length. [user '%{User-Name}', nas '%{NAS-IP-Address}'] -> stop
packet with zero session length. [user '2002 at 192.168.1.5', nas '127.0.0.1']
Tue Aug 12 22:46:20 2014 : Info: [sql] stop packet with zero session
length. [user '2002 at 192.168.1.5', nas '127.0.0.1']

  A Stop packet with zero session length is *stupid*.  The server tosses
those.  Because they're stupid, and don't mean anything.

> Check my log even MySQL date time stamps are wrong also. 

  No.  The server doesn't invent timestamps.  It uses the timestamps it
gets from the NAS.  If the timestamps are wrong, blame the NAS.

  Alan DeKok.