Hello,
We have just installed radiator 2.16.1 on a Windows 2000
Server and it works like a champ. But we did run into one
problem. Radiator was ignoring accounting requests coming
from MegaPOP radius servers and was loging "Bad
authenticator in request" messages. We first made sure that
the shared secrets were correct and then added the
IgnoreAcctSignature parameter. That worked fine and radiator
started accepting the accounting requests.
But the problem is that it does not appear that the remote
megapop servers are recognizing the accounting replies.
Radiator is sending the replies (according to the logs) but
the remote server keeps on resending the requests until it
gives up. That adds several duplicate accounting records to
our database (w/ different AcctDelayTime values). I just
received an email from Megapop support staff claiming that
they have seen this behavior with Radiator running on NT or
2000. They use RADIUS 2.1. Has anyone else run across this?
Is there a patch or fix? Any suggestions are welcome.
Thanks,
Camil Samaha
Intrex
===
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.
