MySQL Backend

[Rampage]

Il 12/06/2012 23:11, Alan DeKok ha scritto:
> Rampage wrote:
>> i also noticed that the radacct table contains one account for each time
>> i perform a login for the specific user, is it normal?
>    That's what your NAS is telling it to do.  The NAS is sending an
> accounting "start" for each login.  And probably no "stop"
>
>

Thanks for your reply,
actually i think a stop is sent because it's registered in the radacct 
table:

mysql> select * from radacct\G
*************************** 1. row ***************************
            radacctid: 1
        acctsessionid: e1dcb98e63c83cb5
         acctuniqueid: f258863473f21879
             username: ciccio
            groupname:
                realm:
         nasipaddress: 192.168.10.1
            nasportid: 2
          nasporttype: Ethernet
        acctstarttime: 2012-06-12 11:28:00
         acctstoptime: 2012-06-12 12:28:00
      acctsessiontime: 3600
        acctauthentic: RADIUS
    connectinfo_start:
     connectinfo_stop:
      acctinputoctets: 5347401
     acctoutputoctets: 66632775
      calledstationid: 192.168.10.1
     callingstationid: 00-0c-29-70-97-19
   acctterminatecause: Session-Timeout
          servicetype: Login-User
       framedprotocol:
      framedipaddress: 192.168.10.103
       acctstartdelay: 0
        acctstopdelay: 0
xascendsessionsvrkey:

acctstoptime seems to be the timestamp of when the NAS sends the stop, 
still the entry from the db is not deleted, so i have an entry for each 
session start, i'm worried that this might cause an infinite database 
grouth in the future when the service goes in production environment.

the NAS is the PfSense captive portal, which afaik is a chillispot.

thanks
Francesco