Hello Jay, On Mar 28, 9:02am, Jay West wrote: > Subject: (RADIATOR) radmin help, additional check/reply items > Ok, I'm probably being obtuse here, but I can't see the forest for the trees > ;) > > We're trying to convert from the default SQL database supplied with radiator > to the default SQL database supplied with radmin. > > There are several reply attributes that we use for every user (and they are > different for each user): FRAMED_FILTER_ID and FRAMED_NETMASK > > These are defined in the RADUSERS file. From what I've seen gazing through > the code (I'm NOT a perl programmer) it would appear that by default these > fields are not used (like they aren't in the default SQL database in > radiator; in radiator you need to explicitly add an AuthSelect that pulls > the CHECKATTR and REPLYATTR data for any extra items, the above two > included). I want to basically do the same thing with the Radmin stuff. I > was thinking you just need to specify an AuthSelect in <AuthBy Radmin> to > return the additional fields, but the plot thickens.... > > In AuthRADMIN.pm, it appears that they already modify the default AuthSelect > (is this perchance documented anywhere?) to include things like > STATICADDRESS, MAXLOGINS, etc. This would make me think I just need to put > in my own AuthSelect in the radius config file, but when looking at that > code it has a comment about pulling extra things from RADCONFIG and > RADATCONFIG. So... this makes me think I might be heading down the wrong > path and not using something that might already be built in. > > So what do I need to do here to have radiator honor these fields in the > radmin database.... just specify an AuthSelect that also selects things like > FRAMED_FILTER_ID and FRAMED_NETMASK, or do I need to hack up AuthRADMIN.pm, > or do I just need to add some stuff to the RADCONFIG and RADATCONFIG tables, > or a combination of the above? Hopefully I'm making SOME sense at least. Yes, perfect sense. While those fields are currently defined int he Radmin schema, they are not (by default) used by AuthBy RADMIN. However. It is easy to add additional fields to the columns that Radiator will honour in AuthBy RADMIN. IN AuthBy RADMIN, you can use AuthSelect and AuthColumnDef to specify _additional_ SQL columns beyond the ones that are used by default. For example, to also get FRAMED_FILTER_ID and FRAMED_NETMASK from the database, and put them in Filter-Id and Framed-IP-Netmask reply attributes, add something like this to your AuthBy RADMIN: AuthSelect ,FRAMED_FILTER_ID,FRAMED_NETMASK AuthColumnDef 0,Filter-Id,reply AuthColumnDef 1,Framed-IP-Netmask,reply Hope that helps. Cheers. > > Any help/advice is most appreciated! > > Jay West > > > === > Archive at http://www.starport.net/~radiator/ > Announcements on [EMAIL PROTECTED] > To unsubscribe, email '[EMAIL PROTECTED]' with > 'unsubscribe radiator' in the body of the message. >-- End of excerpt from Jay West -- Mike McCauley [EMAIL PROTECTED] Open System Consultants Pty. Ltd Unix, Perl, Motif, C++, WWW 24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au Phone +61 3 9598-0985 Fax +61 3 9598-0955 Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, 2000, NT, MacOS X === Archive at http://www.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
