Hello Paul -
At 11:30 +0800 01/1/26, Paul Rolfe wrote:
>Hi,
>
>We have a requirement to authenticate and account for users by proxy
>radius from one location to another. Due to the number of requests
>and speed concerns, it is necessary for us to use Fork and
>Synchronous.
The use of Fork and Synchronous will slow processing dramatically.
Why do you think you have to do this?
>The problem we are seeing however, is that for every fork, the
>client radius server doesn't carry the identifier from the NAS, but
>generates it's own (starting at 1). This breaks duplicate detection
>badly on the destination server, and has forced us to set
>DupInterval to 0 in order for it to even accept the accounting
>packets.
>
>Is there a way to get the forked radius client to send to the remote
>server with the identifier from the NAS? Or is there another
>solution?
>
Just use normal AuthBy RADIUS.
regards
Hugh
--
NB: I am travelling this week, so there may be delays in our correspondence.
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.
