You need to add an Entry in the RadVendors table for the vendor (USR
is 429 I believe) and then you can add entries in the RadAttributes and
RadValues table for the vendor specific attributes and values for that
vendor. When you add a VSA to the RadAttributes table, the
RadAttributeID
is always 26 (Vendor-Specific).
Take a look at this script, as it has VSA updates for USR and many other
popular vendors for a RadiusNT database on MS SQL Server. If you have
an older RadiusNT database you MUST change the primary key on your
RadAttributes and RadValues tables before you can add VSA entries.
> > To complicate matters some, we are waiting for the delivery of an Cisco
> > AS5300, and I don't have a dictionary of Cisco Radius Vendor Attributs. Do
> > I need them ?
> > Where can I get them ?
See the above file. Cisco basically uses a single VSA that is of type
string that you put the Cisco specific information into (you can include
as many of them as needed).
> > A more general question about RadiusNT, is about customising the database.
> > I can see from the list that it is commen practice to change the database
> > layout of RadiusNT.
> > Our setup is quit simple we have users calling into our network with ISDN
> > or Analog and they all use PPP. We can treat all our users the same way,
> > so we don't need alot of different service types. Is there any
> > recommondations about simplifing the database design to acommedate this
> > simple setup, or should we just leave it as it is ?
I'd recommend just leaving it as is. Really the only thing you could
simplify would be to join the MasterAccounts and SubAccounts tables
together.
That doesn't gain you a lot, though.
--Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com
For more information about this list, including removal, pleasesee this URL: http://www.iea-software.com/maillist.html