Why not come to the attributes on Freeradius server after the upgrade to version 3?

Moved to a new server and at the same time decided to update freeradius from 2.2 to 3.0.

Listening on auth address * port 1812
Listening on acct address * port 1813
Listening on auth address 127.0.0.1 port 18120 as server inner-tunnel
Opening new proxy socket 'proxy address * port 0'
Listening on proxy address * port 58434
Ready to process requests
Received Accounting-Request Id 0 from 46.158.248.181:41271 to 172.31.1.100:1813 length 190
server dynamic_client_server {
(0) # Executing section authorize from file /etc/raddb/sites-enabled/dynamic-clients
(0) authorize {
(0) if ("&raw:NAS-Identifier")
(0) if ("&raw:NAS-Identifier") -> TRUE
(0) if ("&raw:NAS-Identifier") {
(0) if ("%{sql: select count(*) from nas where nas.nasidentifier='&raw:NAS-Identifier'}" == 1)
(0) EXPAND %{User-Name}
(0) -->
(0) SQL-User-Name set to "
rlm_sql (sql): Reserved connection (4)
rlm_sql (sql): Executing query: 'select count(*) from nas where nas.nasidentifier='&raw:NAS-Identifier"
rlm_sql (sql): Released connection (4)
rlm_sql (sql): Closing connection (0), from 1 unused connections
rlm_sql_mysql: Socket destructor called, closing socket
(0) EXPAND %{sql: select count(*) from nas where nas.nasidentifier='&raw:NAS-Identifier'}
(0) --> 0
(0) if ("%{sql: select count(*) from nas where nas.nasidentifier='&raw:NAS-Identifier'}" == 1) -> FALSE
(0) } # if ("&raw:NAS-Identifier") = notfound
(0) } # authorize = notfound
} # server dynamic_client_server
Ignoring request to the acct address * port 1813 from unknown client 46.158.248.181 41271 port proto udp


In %{User-Name} and NAS-Identifier - null values.

Has anyone been faced with the question of relocation, perhaps that is the problem?
There is a suspicion that somewhere nakosyachili with obtaining most of these attributes.

The same router authenticates fine on the old server.

radiusd -X https://yadi.sk/i/hgSzN58cvLaXH
July 4th 19 at 23:28
0 answer

Find more questions by tags FreeRADIUSMySQL