FreeRADIUS does not recognize device added in the NAS table

james.ngobui at james.ngobui at
Sun Sep 30 17:20:14 CEST 2018

Hey Alan,
Thank you for your instruction. I did restart both RADIUS and SQL (Apache2) server but still...
However, I found out that, the field "nasname" should actually be the IP address of the nas (in my case, it is an access point) instead of the name PopUpOff. And also, the field "server" should be left blank (NULL). 
So after changing those fields and restart the server again, it is working now!
But thank you very much for your helps and instructions
Kind regards

-----Original Message-----
From: Freeradius-Users < at> On Behalf Of Alan DeKok
Sent: September 30, 2018 4:17 AM
To: FreeRadius users mailing list <freeradius-users at>
Subject: Re: FreeRADIUS does not recognize device added in the NAS table

On Sep 29, 2018, at 10:39 PM, James Ngo <james.ngobui at> wrote:
> Below is the log file content. I highlight one Error that is failed to 
> resolve the Nasname PopUpOff to IPv4, etc.... so I changed to the NAS 
> IP address but that did not work either.

  Yes, it does work.  If you read the debug output, you see that it's reading the NAS table when the server *starts*.

  And you didn't restart the server after changing the NAS table.

> ----------------------------------------------------------------------
> -----------------------------
> Sat Sep 29 18:06:41 2018 : Info: rlm_sql (sql): Opening additional 
> connection (31), 1 of 31 pending slots used

  Use "radiusd -X".  Honestly... this is documented *everywhere*.

> *Sat Sep 29 18:34:19 2018 : Error: Failed resolving "PopUpOff" to IPv4
> address: Name or service not known*

  Which means that the client is unknown.

  Did you try restarting the server *after* fixing the SQL database?

  Alan DeKok.

List info/subscribe/unsubscribe? See

This email has been checked for viruses by AVG.

More information about the Freeradius-Users mailing list