I was having problems with the evaluation complaining about a license, so I
decided to rebuild the entire OpenWRT installation from scratch.
Went through the process, installed Perl and copied/untar'd Radiator as per
FAQ (http://www.open.com.au/radiator/faq.html#188), but when I run radiusd,
I get
http://hayesqeci.carpettediem.fr/fipugo.html Protect YourBe dDesir e
Ovecrome ro'ds sofftness
Your doze of male energy
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
Hi Hugh:
Any update regarding the Radiator issue with AD 2008 schema and ADSI auth ?
Regards,
Adrian
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
Hello Adrian -
I would suspect a difference in the configuration of the AD 2008 schema and/or
the user settings therein.
Have you checked the log messages from AD 2008?
As mentioned previously, I would be more inclined to use the AuthBy NTLM clause
on *NIX, or the AuthBy LSA clause on Windows
Hello Andrea -
It looks like Perl is missing "POSIX.pm" (at least) so I would suspect that
Perl does not have all its additional modules installed.
regards
Hugh
On 23 Aug 2010, at 19:56, Andrea Coppini (AIR Networks) wrote:
> I was having problems with the evaluation complaining about a lic
Hello Mark -
Can you please send me a copy of the full configuration file and a trace 4
debug showing the startup messages and a more complete log showing the whole
sequence?
thanks and regards
Hugh
On 21 Aug 2010, at 01:10, Pearson, Mark wrote:
> Hi, I currently have Radiator for Windows
I have a set of Radiator with frontend and backends on the same server.
Sometimes I see warnings in the logfile like that:
Mon Aug 23 21:51:20 2010: WARNING: Unknown reply received in AuthRADIUS
for request 138 from 127.0.0.1:1650
What reasons it can be for this? Overload? Is it possible to avoi
Hello Arthur -
The usual cause for this is your Radiator server has timed out and sent a retry
before the first reply has come back.
The first reply then comes back which Radiator processes normally, then the
second reply comes back but Radiator has already dealt with the request with
the fir
