18. How do I set up automatic IP address allocation
Basically, you need to do 2 things:
- Add 1 or more FramedGroupBaseAddress items to each Client in your
Radiator configuration file.
- Add a Framed-Group reply item to each user for whom you want address
allocation.
For example in the Radiator configuration file:
# This is the base address for Framed-Group = 0
FramedGroupBaseAddress 10.0.0.1
# This is the base address for Framed-Group = 1
FramedGroupBaseAddress 10.0.1.1
# This is the base address for Framed-Group = 2
FramedGroupBaseAddress 10.0.2.1
.....
and in the users file, something like:
mikem Password = "fred"
Framed-Group = 1,
Framed-Protocol = PPP,
etc.
Now if mikem logs into the Client at port 5, he will be allocated an IP
address of 10.0.1.6 (ie 10.0.1.1 + 5). If the users file said
Framed-Group = 0, and he logged in on port 11, he would be allocated an
IP address of 10.0.0.12 (10.0.0.1 + 11).
19. How do I make Radiator work with Emerald?
Emerald is a good ISP billing system
from IEA. It uses Microsoft SQL database for user and billing data.
IEA also offer an NT based radius server called RadiusNT that
can authenticate from and insert accounting into Emerald.
Radiator can also authenticate from and insert accounting into
Emerald, but with Radiator, you can do it from a Unix host, and with
the extra features that Radiator has but RadiusNT does not.
There is an example Radiator configuration file in goodies/emerald.cfg
in the Radiator distribution. Use it as a starting point for
integrating with Emerald. You will need to configure some attributes like
DBSource, DBUsername and DBAuth to suit your Emerald setup. You will
most likely want to use ODBC to connect to the Emerald MSSQL
database, but you could also use the Sybase driver, if you have that
instead.
20. How do I make Radiator work with LDAP on NT?
Follow these steps:
- Make sure you have installed the Perl NT binaries from Gurusamy Sarathy.
- Fetch and install NETSCAPE DIRECTORY SDK 1.0 Win32 for Windows NT with SSL support (self-extracting archive)
- Fetch and install the Net-LDAP Windows NT Binaries v1.40.
Make sure you follow all the instructions in the Readme file.
- Configure an clause in your Radiator configuration file.
See the example radius.cfg in the Radiator distribution for examples.
21. How do I make Radiator work with Platypus?
Platypus is an excellent ISP
billing system
from Boardtown. It uses Microsoft SQL database for user and billing
data.
Radiator can authenticate from and insert accounting into
Platypus. This makes for seamless integration between your
radius server and your customer management/billing system. Using ODBC,
you can run your radius server on Unix, Win95 or NT.
There is an example Radiator configuration file in goodies/platypus.cfg
in the Radiator distribution. Use it as a starting point for
integrating with Platypus.
You will need to configure some attributes like
DBSource, DBUsername and DBAuth to suit your PLatypus setup. You will
most likely want to use ODBC to connect to the Platypus MSSQL
database, but you could also use the Sybase driver, if you have that
instead.
22. How can I apply the same check or reply items to all the users in my SQL database?
Sometimes you need to have a common set of check or reply items for
all users, but you dont want to have to put them in every user
in the database. Or maybe you want to be able to tune them for all
users easily.
You can arrange for Radiator to cascade from SQL to a flat file
or other user database.
AuthByPolicy ContinueWhileAccept
...
...
(See goodies/common-sql.cfg for example code).
You can then have a DEFAULT user in the users file specified in the
AuthBy FILE with the common reply items you want:
DEFAULT Service-Type = Framed-User
Framed-Protocol = PPP,
Framed-IP-Netmask = 255.255.255.0,
Framed-Routing = None,
Framed-MTU = 1500,
Framed-Compression = Van-Jacobson-TCP-IP
Another alternative is to fall cascade from SQL to another SQL that
only selects the check and reply items for a DEFAULT user:
AuthByPolicy ContinueWhileAccept
...
AuthSelect select NULL, CHECKATTR, REPLYATTR from SUBSCRIBERS \
where USERNAME = 'DEFAULT';
With some (but not all: mSQL does not support it) SQL servers you
provide common check and reply items more easily with a special
AuthSelect statement:
AuthSelect select PASSWORD, 'Service-Type = Framed-User',
'Framed-Protocol = PPP, etc etc etc'
from SUBSCRIBERS where USERNAME = '%n'
With some SQL servers (eg Oracle), you could even combine the common
and per-user check and reply items by using concatenation in the
select statement.
23. How can I make Radiator work with the PPTP server?
Changes are outlined in Microsoft
Online Support article Q172216.
- Start Regedit
- Goto: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP
- Click on SPAP, click Edit, and Delete. Yes to confirm deletion.
- Click on CHAP, click Edit, and Delete. Yes to confirm deletion.
- Close Regedit, stop and restart Routing and Remote Access Service.
(Contributed by Dalton, Robert W (Robert.Dalton@88CG.WPAFB.AF.MIL))
24. How can I connect to Microsoft SQL server from Unix using OpenLink?
The best option is to use the "Combined OpenLinkODBC/iODBC package" from
OpenLink. This package
(smkoxxxx.taz for Solaris) allows
ODBC requests to be sent by RPC from your Unix client to (for example) an NT
host running Miscrosoft SQL Server 6. It really does work.
You will also need the OpenLink request broker for NT (ntadm65x.zip)
installed on the NT host where the MS-SQL server is running. This broker
receives RPC calls from the iODBC package on the Unix host and
translates them into MS-SQL
calls. After installation, start the Oplrqb.exe program.
Further, you will have to build
DBD-ODBC 0.16 or better on your Unix host
to use the include files and libraries that come
with the OpenLinkODBC/iODBC package (this will involve some minor changes
to Makefile.PL before building DBD-ODBC. Change
my $myodbc = 'odbc'; # edit and hack to suit!
to
my $myodbc = 'iodbc'; # edit and hack to suit!
and add a line at:
print SQLH qq{#include <iodbc.h>\n}; # ADD this line
print SQLH qq{#include <isql.h>\n};
print SQLH qq{#include <isqlext.h>\n};
You will also need to create ~/.odbc.ini on the Unix host as descibed in
the OpenLinkODBC/iODBC package, as well as create /etc/udbc.ini with
something like this:
[radius_udbc]
Description = Sample MS SQLServer DSN
Host = fred
ServerType = SQLServer 6
ServerOptions =
Database = radius
FetchBufferSize = 30
If your wanted to connect to a Platypus database on NT, you would put
something like this in udbc.ini:
[plat_udbc]
Description = Sample MS SQLServer DSN
Host = fred
ServerType = SQLServer 6
ServerOptions =
Database = plat
FetchBufferSize = 30
Finally, you would specify something like this in the Radiator config
file for your AuthBy SQL:
DBSource dbi:ODBC:radius_udbc
DBUsername sa
DBAuth sa
