Fajar, I use -X mode and my NAS send a complete information. In the same request I got an "invalid" insert and the I receive a valid insert. In the same NAS I have about 400 users and one or other have a "wrong" insert!! In FreeRadius 2.2.9 I don't have this problem. I know.... this is not a FreeRadius problem, but I want a hint to solve this! Thanks Em 08/08/2017 12:11, Fajar A. Nugraha escreveu:
On Tue, Aug 8, 2017 at 8:04 PM, Aurélio de Souza Ribeiro Neto <netolistas@mpc.com.br> wrote:
Fajar,
I did and not appear to be a Query problem.
Look the first and the second insert:
INSERT INTO radacct (acctsessionid, acctuniqueid, username, realm, nasipaddress, nasportid, nasporttype, acctstarttime, acctupdatetime, acctstoptime, acctsessiontime, acctauthentic, connectinfo_start, connectinfo_stop, acctinputoctets, acctoutputoctets, calledstationid, callingstationid, acctterminatecause, servicetype, framedprotocol, framedipaddress) VALUES ('81b0ec6b', '1e485bcb3cfbe8526b33e4d1fb50fecd', 'katiasantos', '', '172.17.43.2', '15791310', '', (NOW() - 0), NOW(), NOW(), 0, '', '', '', '0' << 32 | '0', '0' 'Framed-User', 'PPP', '187.120.203.169');
INSERT INTO radacct (acctsessionid, acctuniqueid, username, realm, nasipaddress, nasportid, nasporttype, acctstarttime, acctupdatetime, acctstoptime, acctsessiontime, acctauthentic, connectinfo_start, connectinfo_stop, acctinputoctets, acctoutputoctets, calledstationid, callingstationid, acctterminatecause, servicetype, framedprotocol, framedipaddress) VALUES ('81b0ecc1', '5b68881f4438da10588f26dbe616c917', 'katiasantos', '', '172.17.43.2', '15791396', 'Ethernet', NOW(), NOW(), NULL, '0', 'RADIUS', '', '', '0', '0', 'CE - POP SM8', '1C:7E:E5:C4:2E:73', '', 'Framed-User', 'PPP', '187.120.203.169');
What I can do?
Then you need to capture what the NAS send when this happens. On the first insert, FR believes that the NAS is not sending nasporttype and callingstationid. 'freeradius -X' can show you what FR receives (I did not see accounting request on your original dump, only Access-Request).
Again, my GUESS is the NAS sends it that way. In which case you need to ask whoever configured the NAS (or its creators) why it sends that.