Some Android smartphones send only accounting request

Riccardo locatelli riccardo.locatelli at netweek.it
Wed Aug 19 15:19:55 CEST 2015


Hi

Today I tested again.
I verified that the Acct-Session-Id is always different (if not that is why
I made server restarts or the AP).


mysql> select * from radacct where username = 'test' \G;
*************************** 1. row ***************************
           radacctid: 7180
            username: test
       acctstarttime: 2015-08-19 15:09:00
        acctstoptime: NULL
     acctsessiontime: 0
     acctinputoctets: 0
    acctoutputoctets: 0
     framedipaddress: 192.168.1.33
       acctsessionid: 55CE1818-0000003E
        acctuniqueid: 40c8870e31443b84
           groupname:
               realm:
        nasipaddress: 192.168.100.110
           nasportid: 0
         nasporttype: Wireless-802.11
       acctauthentic: RADIUS
   connectinfo_start: CONNECT 0Mbps 802.11b
    connectinfo_stop:
     calledstationid: 02-18-1A-7A-91-3C:Netweek
    callingstationid: 78-4B-87-67-A9-1C
  acctterminatecause:
         servicetype:
      framedprotocol:
      acctstartdelay: 0
       acctstopdelay: 0
xascendsessionsvrkey:
*************************** 2. row ***************************
           radacctid: 7177
            username: test
       acctstarttime: 2015-08-19 15:07:37
        acctstoptime: 2015-08-19 15:07:41
     acctsessiontime: 5
     acctinputoctets: 0
    acctoutputoctets: 0
     framedipaddress: 192.168.1.33
       acctsessionid: 55CE1818-0000003D
        acctuniqueid: 2c187cf69d3da15b
           groupname:
               realm:
        nasipaddress: 192.168.100.110
           nasportid: 0
         nasporttype: Wireless-802.11
       acctauthentic: RADIUS
   connectinfo_start: CONNECT 0Mbps 802.11b
    connectinfo_stop: CONNECT 0Mbps 802.11b
     calledstationid: 02-18-1A-7A-91-3C:Netweek
    callingstationid: 78-4B-87-67-A9-1C
  acctterminatecause: Lost-Carrier
         servicetype:
      framedprotocol:
      acctstartdelay: 0
       acctstopdelay: 0
xascendsessionsvrkey:
*************************** 3. row ***************************
           radacctid: 7178
            username: test
       acctstarttime: 2015-08-19 15:07:48
        acctstoptime: 2015-08-19 15:08:45
     acctsessiontime: 58
     acctinputoctets: 109886
    acctoutputoctets: 50726
     framedipaddress: 192.168.1.33
       acctsessionid: 55CE1818-00000040
        acctuniqueid: 5cb5ddb790e72af3
           groupname:
               realm:
        nasipaddress: 192.168.100.110
           nasportid: 0
         nasporttype: Wireless-802.11
       acctauthentic: RADIUS
   connectinfo_start: CONNECT 0Mbps 802.11b
    connectinfo_stop: CONNECT 0Mbps 802.11b
     calledstationid: 00-18-0A-7A-91-3C:Netweek
    callingstationid: 78-4B-87-67-A9-1C
  acctterminatecause: Lost-Carrier
         servicetype:
      framedprotocol:
      acctstartdelay: 0
       acctstopdelay: 0
xascendsessionsvrkey:
3 rows in set (0.00 sec)



When i disconnect my smartphone nas send Acct-Status-Type = Stop
When i reconnect my smartphone nas send Acct-Status-Type = Start
Acct-Session-Id is different for each session.
it seems that radius does not understand that it are different sessions...

It may have a bug? Help!

2015-08-18 15:45 GMT+02:00 Nick Lowe <nick.lowe at gmail.com>:

> You can look to disable the roaming features on your APs but that would be
> horrible from a user experience perspective as there would be
> back-and-forth to the RADIUS server whenever a roam from one BSS to another
> occurred. You are quite likely to cause interruption in service therefore.
>
> Why not instead fix your logging / session correlation?
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>



-- 
Riccardo Locatelli


More information about the Freeradius-Users mailing list