Yes, you can specify a network, not just single IP address. Ivan Kalik Kalik Informatika ISP
Dana 12/4/2008, "Tuc at T-B-O-H.NET" <[EMAIL PROTECTED]> piše: >Hi Ivan, > > Thanks for the reply. I think its starting to sink in. :) >I have to test out how we'll do a bit of it, but I think I get the >jist of it. I don't see how any of the netmask, require_message_authenticator >or virtual_server fit into it... But since I wasn't using it anyway, I >won't push my luck. ;) (Unless for netmask your saying the nasname >could be 192.168.3.0/24) > > Thanks, Tuc >> >> nasname on your AP goes into NAS-Identifier filed in access request. >> It's not the same as nasname in nas table which takes NAS IP or FQDN. >> You can put it in shortname filed. "Secret per NAS" = "Secret per NAS >> IP address". >> >> Ivan Kalik >> Kalik Informatika ISP >> >> Dana 11/4/2008, "Tuc at T-B-O-H.NET" <[EMAIL PROTECTED]> piše: >> >> >Hi, >> > >> > If I choose DNS name, and I don't fully qualify it, >> >does it follow the standard BIND rules of using the "domain" >> >setting, or going down the "search" path? >> > >> > Reason I'm trying to avoid the IP or the FQDN is that >> >I was hoping to use the nasname along with the secret in >> >the UAM program I'm using for a "Secret per NAS" situation. >> >The hotspots are already using just a nasname currently (Which >> >is just something like SBC-1427). (Then again, getting the >> >client to put all the NAS into DNS is going to be a tough >> >sell too) >> > >> > Thanks, Tuc >> >> >> >> IP address (or DNS name) goes into nasname field. >> >> >> >> Ivan Kalik >> >> Kalik Informatika ISP >> >> >> >> >> >> Dana 11/4/2008, "Tuc at T-B-O-H.NET" <[EMAIL PROTECTED]> piše: >> >> >> >> >Hi, >> >> > >> >> > I had actually kept this email in my queue to implement >> >> >someday. Today is someday. But I have a question. >> >> > >> >> > The config file contains IP addresses, which the nas.sql >> >> >doesn't. How do I sync up the format of the clients.conf with >> >> >the nas.sql? >> >> > >> >> >client nas_shortname { >> >> > ipaddr = ?????????? >> >> > (or) >> >> > ipv6addr = ???????? >> >> > netmask = ???????? >> >> > secret = nas_secret >> >> > require_message_authenticator = ???????? >> >> > shortname = nas_shortname >> >> > nastype = nas_type >> >> > virtual_server = ???????? >> >> >} >> >> > >> >> > Thanks, Tuc >> >> >> >> >> >> Hi, >> >> >> >> >> >> in sql.conf it says: >> >> >> >> >> >> Set readclients to 'yes' to read radius clients from the database >> >> >> ('nas' table) >> >> >> Clients will ONLY be read on server startup. For performance >> >> >> and security reasons, finding clients via SQL queries CANNOT >> >> >> be done "live" while the server is running. >> >> >> >> >> >> Best, >> >> >> Walter >> >> >> >> >> >> >> >> >> Am 22.01.2008 um 19:30 schrieb Pawel Cieplinski: >> >> >> >> >> >> > Hi there >> >> >> > >> >> >> > >> >> >> > >> >> >> > Everything works fine so far, but after adding a new NAS to DB, >> >> >> > radius server need restart to read this data, I am trying to >> >> >> > manipulate nas list without restarting freeradius, but due to lack >> >> >> > od documentation could you help me with that please. >> >> >> > >> >> >> > >> >> >> > >> >> >> > Pawel Cieplinski >> > >> > >> > >> >> - >> List info/subscribe/unsubscribe? See >> http://www.freeradius.org/list/users.html >> >> > > > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html