January 2008 - Freeradius-Users - lists.freeradius.org

Re: question
by Raghu V S 02 Jan '08

02 Jan '08

Hi sir, i am using freeradius server version(1.1.7) initially i sent some request to server (radiusd),it was turned failure by server. now is there any way, so that "without restarting the server (radiusd)" , further requests can be sent and get processed by the server. thank you best regards, ----- Original Message ----- From: <freeradius-users-request(a)lists.freeradius.org> To: <freeradius-users(a)lists.freeradius.org> Sent: Monday, December 31, 2007 4:30 PM Subject: Freeradius-Users Digest, Vol 32, Issue 84 > Send Freeradius-Users mailing list submissions to > freeradius-users(a)lists.freeradius.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freeradius.org/mailman/listinfo/freeradius-users > or, via email, send a message with subject or body 'help' to > freeradius-users-request(a)lists.freeradius.org > > You can reach the person managing the list at > freeradius-users-owner(a)lists.freeradius.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Freeradius-Users digest..." > > > Today's Topics: > > 1. clients.conf and SQL? (Tuc at T-B-O-H.NET) > 2. RE: (Raghu V S) > 3. Re: (liran tal) > 4. Re: clients.conf and SQL? (liran tal) > 5. Re: (Marinko Tarlac) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 30 Dec 2007 20:15:27 -0500 (EST) > From: "Tuc at T-B-O-H.NET" <ml(a)t-b-o-h.net> > Subject: clients.conf and SQL? > To: freeradius-users(a)lists.freeradius.org > Message-ID: > <200712310115.lBV1FRDO012471(a)himinbjorg.tucs-beachin-obx-house.com> > Content-Type: text/plain; charset=us-ascii > > Hi, > > I can't seem to find any reference to making the > contents of the clients.conf accessible via SQL. We are > constantly making edits, and having to constantly reload > the server doesn't make sense. > > Pointers to where I missed putting it into > MySQL, or if anyone knows how to would be appreciated. > > Thanks, Tuc > > > ------------------------------ > > Message: 2 > Date: Mon, 31 Dec 2007 10:59:30 +0530 > From: "Raghu V S" <raghu.vs(a)lifetreeindia.com> > Subject: RE: > To: <freeradius-users(a)lists.freeradius.org> > Message-ID: <000201c84b72$a71befc0$a901a8c0@Raghu> > Content-Type: text/plain; charset="iso-8859-1" > > initially started radius with (radiusd command). > > then once more gave the cmmand (radiusd -x) > output was as follows... > > " Starting - reading configuration files ... > Using deprecated naslist file. Support for this will go away soon. > There appears to be another RADIUS server running on the authentication > port 1812" > > how restart the server in debug mode? >

2 1

RE:
by Raghu V S 01 Jan '08

01 Jan '08

initially started radius with (radiusd command). then once more gave the cmmand (radiusd -x) output was as follows... " Starting - reading configuration files ... Using deprecated naslist file. Support for this will go away soon. There appears to be another RADIUS server running on the authentication port 1812" how restart the server in debug mode?

4 3

Two 'secret' entries in clients.conf
by jonr＠destar.net 01 Jan '08

01 Jan '08

Hello, Our network group is going to be changing the 'secret' for all of their gear but they are going to do it in stages. I was wondering if there is a way to have two 'secret' entries in the clients.conf file. Leave the original until the change is complete and have the new 'secret' also available for the devices that have changed their 'secret'. I saw in the wiki(http://wiki.freeradius.org/index.php/Clients.conf) this little bit of the config and was wondering if it would work. The only difference in the below portion of that page is one has a /24 and the other a /16 also the 'shortname' is different. Can the two stanzas both have the same CIDR and can the 'shortnames' be the same or do they have to be different? Thanks for any ideas, Jon # # You can now specify one secret for a network of clients. # When a client request comes in, the BEST match is chosen. # i.e. The entry from the smallest possible network. # #client 192.168.0.0/24 { # secret = testing123-1 # shortname = private-network-1 #} # #client 192.168.0.0/16 { # secret = testing123-2 # shortname = private-network-2 #}

2 1