Hello Carles -
This is actually a bit tricky, as the AuthBy RADIUS clause normally
behaves somewhat differently to the other AuthBy clauses. Will it
matter in your operation if the NAS receives two Access-Accept and
Accounting-Accept messages? And will the RADIATOR2 host have the same
users and so on as RADIATOR1? And finally how busy is your system -
will it be a problem if it runs slower in case of problems? The
answers to these questions will determine the best way to set up the
tests.
Alternatively of course, you can always (and you should anyway) test
your setup with "radpwtst". There are parameters to run multiple
iterations so you can do load tests and elapsed time tests.
thanks
Hugh
At 12:59 +0200 17/8/00, Carles Xavier Munyoz Bald� wrote:
>Hugh Irvine wrote:
>> If you send me your existing configuration file, I will show you what
>> to do. Could also please explain exactly what you want to happen with
>> RADIATOR2?
>
>RADIATOR1 is my actual production radius system.
>RADIATOR2 is a new radius system formed by varios radius hosts and a
>load balancing device that gives us high avaibility and scalability.
>Our intention is test if the new radius system used in RADIATOR2 can
>handle the Authentication/Accounting packets received by RADIATOR1 and
>test the high avaibility mecanism.
>This is the reason for which we want that RADIATOR2 receives all the
>Authentication/Accounting packets received by RADIATOR1 but if there is
>a communication problem between RADIATOR1 and RADIATOR2 don't bother the
>production radius system.
>
>Here is our configuration file:
>PidFile ./tmp/radiusd.pid
>AuthPort 1812
>AcctPort 1813
># BindAddress 0.0.0.0
>LogDir ./logs
>DbDir ./db
>DictionaryFile ./etc/dictionary.ascend
>
><Client 10.10.10.10>
> Secret ssssssssssss
> DupInterval 0
> IdenticalClients 10.10.10.11
></Client>
>
><Client 20.20.20.20>
> Secret sssssssssss
> NasType AscendSNMP
> SNMPCommunity ccccccc
> IdenticalClients 20.20.20.21
></Client>
>
><SessionDatabase SQL>
> Identifier DBSSQL
> DBSource dbi:mysql:radius:1.1.1.1
> DBUsername user
> DBAuth pass
> AddQuery insert into ONLINE (USERNAME, NASIDENTIFIER, NASPORT, \
> ACCTSESSIONID, TIME_STAMP, FRAMEDADDRESS, PORTTYPE, \
> SERVICETYPE) values ('%n', '%N',
>%{NAS-Port},'%{Acct-Session-Id}', \
> %{Timestamp}, '%{Framed-Address}',
>'%{NAS-Port-Type}','%{Service-Type}')
> DeleteQuery delete from ONLINE where \
> NASIDENTIFIER='%N' and NASPORT=%{NAS-Port}
> ClearNasQuery delete from ONLINE where NASIDENTIFIER='%N'
> CountQuery select NASIDENTIFIER, NASPORT, ACCTSESSIONID from
>RADONLINE \
> where USERNAME='%n'
></SessionDatabase>
>
><Log FILE>
> Filename %L/logfile
> Trace 2
></Log>
>
><Realm /^myrealm/>
> SessionDatabase DBSSQL
> MaxSessions 1
> RewriteUsername s/^([^@]+).*/$1/
> AcctLogFileName %L/detail
> AccountingHandled
> <AuthBy DBFILE>
> Filename %D/users
> </AuthBy>
></Realm>
>
><Realm DEFAULT>
> <AuthBy FILE>
> Filename %D/reject
> </AuthBy>
></Realm>
>
>
>May you help us with the configuration ?
>
>Greetings.
>---
>Carles Xavier Munyoz Bald� / [EMAIL PROTECTED]
>Wanadoo Espa�a
>Dpto. Sistemas / System Department
>Tel: +34 96 5040000 Ext. 40046 - Fax: +34 96 5040047
>http://www.wanadoo.es/
>---
--
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/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.
