freeradius-server

freeradius-server copied to clipboard

What type of defect/bug is this?

Unexpected behaviour (obvious or verified by project member)

How can the issue be reproduced?

For my case, Use Ruckus Access-Point with Wireless Controller. Broadcast a Hotspot SSID with captive portal (landing page), point the authentication and accounting to a Ubuntu 22.04.3 Linux server installed FreeRadius 3.0.26 and MySQL 8.0.35. My captive portal is in the same server. My Ruckus Wireless Controller is set to periodically send accounting update to the radius accounting server every 10 minutes.

First, Use laptop connect SSID and then the landing page show. Next, click the accept button in landing page. Then, waiting the response from web server and then the web page jump to an website which is set in the Ruckus Wireless Controller, such as google.com Then, the laptop can go to Internet. Then, wait 10 mins for the radius accounting update from Wireless Controller to the FreeRadius server. After update, the mysql database radius.radacct table show that the acctsessiontime is 600 which is 600 seconds = 10 mins. After update, turn off the Wi-Fi on the laptop. Then, wait 1 minute. Then, turn on the Wi-Fi on the laptop. Then, use laptop connect SSID and login the landing page again. Then, the acctsessiontime is reset to less than 600. I have a workaround solution for that. Remove the "UNIQUE KEY acctuniqueid (acctuniqueid)" in the radius.radacct table Edit /etc/freeradius/3.0/mods-config/sql/main/mysql/queries.conf file Revise all queries with condition of AcctUniqueId as below. From: WHERE AcctUniqueId = '%{Acct-Unique-Session-Id}' To: WHERE AcctUniqueId = '%{Acct-Unique-Session-Id}' and radacctid = (select * from (select max(radacctid) from ${....acct_table2} where AcctUniqueId = '%{Acct-Unique-Session-Id}') as a)" Restart FreeRadius service

Log output from the FreeRADIUS daemon

no

Relevant log output from client utilities

no

Backtrace from LLDB or GDB

no

There is unsufficient information here for us to do anything.

When you opened this issue, the default template had explicit instructions on what to do, and what information we need. Please give us the information which was already requested.

Looks like configuration needed for a particular NAS issue, not a FreeRADIUS bug.