nas table in rlm_sql module - usage
Hi!! I was trying to find out what is this table nas really used for. I read the whole documentation in the doc directory of radius and dialup_admin but I still have many doubts. Is it used just for mapping and getting information about online users or it is somehow equivalent to clients.conf file?? Please give me o short explanation of this issue. Thank you in advance:) Cheers tomasz
On Fri, 9 Feb 2007, tzieleniewski wrote:
I was trying to find out what is this table nas really used for. I read the whole documentation in the doc directory of radius and dialup_admin but I still have many doubts. Is it used just for mapping and getting information about online users or it is somehow equivalent to clients.conf file??
It's the SQL equivalent of clients.conf, yes. -- Jeremy L. Gaddis, MCP, GCWN jeremy@linuxwiz.net LinuxWiz Consulting http://linuxwiz.net
On Fri, 9 Feb 2007, TZieleniewski wrote:
so clients.conf can be empty and all settings can be contained in nas table?
Yes.
will sql work for ip6 client??
No idea. -- Jeremy L. Gaddis, MCP, GCWN jeremy@linuxwiz.net LinuxWiz Consulting http://linuxwiz.net
Gaddis, Jeremy L.-2 wrote:
On Fri, 9 Feb 2007, TZieleniewski wrote:
so clients.conf can be empty and all settings can be contained in nas table?
Is there some spot where we can get definitions for each column (like where each definition maps to in the clients.conf file)? Does it work out like (naming from clients.conf -> nas.sql) client -> each row in the table hostname|ipaddress -> nasname shortname -> shortname nastype -> type ??-> ports secret-> secret ??-> communities ??-> description (this just a string we put in for us?) -- View this message in context: http://www.nabble.com/nas-table-in-rlm_sql-module---usage-tf3201294.html#a88... Sent from the FreeRadius - User mailing list archive at Nabble.com.
What I managed to figure out is that nasname is a source for a name to ip resolving. So probably the nasname has to be different (its ip resolution) from the one specified in the clients.conf file. Well those of course are only my suggestions:) Cheers -tomasz
Gaddis, Jeremy L.-2 wrote:
On Fri, 9 Feb 2007, TZieleniewski wrote:
so clients.conf can be empty and all settings can be contained in nas table?
Is there some spot where we can get definitions for each column (like where each definition maps to in the clients.conf file)? Does it work out like (naming from clients.conf -> nas.sql) client -> each row in the table hostname|ipaddress -> nasname shortname -> shortname nastype -> type ??-> ports secret-> secret ??-> communities ??-> description (this just a string we put in for us?)
-- View this message in context: http://www.nabble.com/nas-table-in-rlm_sql-module---usage-tf3201294.html#a88... Sent from the FreeRadius - User mailing list archive at Nabble.com.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Is there anything I have to config so it doesn't touch the config files? How do I move the server onto pure SQL for the NAS list? Can the clients.conf file be totally empty? tzieleniewski wrote:
What I managed to figure out is that nasname is a source for a name to ip resolving. So probably the nasname has to be different (its ip resolution) from the one specified in the clients.conf file. Well those of course are only my suggestions:)
Cheers -tomasz
-- View this message in context: http://www.nabble.com/nas-table-in-rlm_sql-module---usage-tf3201294.html#a88... Sent from the FreeRadius - User mailing list archive at Nabble.com.
Yes I checked it. You may comment it out from the radiusd.conf file.
Is there anything I have to config so it doesn't touch the config files? How do I move the server onto pure SQL for the NAS list? Can the clients.conf file be totally empty?
tzieleniewski wrote:
What I managed to figure out is that nasname is a source for a name to ip resolving. So probably the nasname has to be different (its ip resolution) from the one specified in the clients.conf file. Well those of course are only my suggestions:)
Cheers -tomasz
-- View this message in context: http://www.nabble.com/nas-table-in-rlm_sql-module---usage-tf3201294.html#a88... Sent from the FreeRadius - User mailing list archive at Nabble.com.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
But actually there is one place where U will need clients.conf. If U use log_badlogins from dialup_admin/bin scripts you are going to need it if to have the nasipaddress logged too. It will be than display in the failed logins dialup_admin screen. Still it will be displayed in the form of name not IP address. Personally I would like to have it displayed as the IP but I don't know how to set it this way. Maybe someone can help us?:) Cheers
Yes I checked it. You may comment it out from the radiusd.conf file.
Is there anything I have to config so it doesn't touch the config files? How do I move the server onto pure SQL for the NAS list? Can the clients.conf file be totally empty?
tzieleniewski wrote:
What I managed to figure out is that nasname is a source for a name to ip resolving. So probably the nasname has to be different (its ip resolution) from the one specified in the clients.conf file. Well those of course are only my suggestions:)
Cheers -tomasz
-- View this message in context: http://www.nabble.com/nas-table-in-rlm_sql-module---usage-tf3201294.html#a88... Sent from the FreeRadius - User mailing list archive at Nabble.com.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
SQL refuses to start when I comment out the INCLUDE line with clients.conf. Is there anything else I have to change so that it knows to look to SQL for a table of acceptable NAS's and to get it to run other than commenting out this INCLUDE statement? tzieleniewski wrote:
Yes I checked it. You may comment it out from the radiusd.conf file.
Is there anything I have to config so it doesn't touch the config files? How do I move the server onto pure SQL for the NAS list? Can the clients.conf file be totally empty?
tzieleniewski wrote:
What I managed to figure out is that nasname is a source for a name to
ip
resolving. So probably the nasname has to be different (its ip resolution) from the one specified in the clients.conf file. Well those of course are only my suggestions:)
Cheers -tomasz
-- View this message in context: http://www.nabble.com/nas-table-in-rlm_sql-module---usage-tf3201294.html#a88... Sent from the FreeRadius - User mailing list archive at Nabble.com.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- View this message in context: http://www.nabble.com/nas-table-in-rlm_sql-module---usage-tf3201294.html#a89... Sent from the FreeRadius - User mailing list archive at Nabble.com.
Hi,
SQL refuses to start when I comment out the INCLUDE line with clients.conf. Is there anything else I have to change so that it knows to look to SQL for a table of acceptable NAS's and to get it to run other than commenting out this INCLUDE statement?
last time I looked, you still had to have a stub clients.conf - even with just a fake client in it. to USE the NAS SQL table, simply look at the bottom few lines of sql.conf - its self documented! # Set to 'yes' to read radius clients from the database ('nas' table) readclients = yes ensure that the other lines in sql.conf are okay eg nas_table = "nas" # NAS Query nas_query = "SELECT id, nasname, shortname, type, secret FROM ${nas_table}" alan
participants (5)
-
A.L.M.Buxey＠lboro.ac.uk -
ChristosH -
Gaddis, Jeremy L. -
tzieleniewski -
TZieleniewski