Doug Hardie wrote:
I am a bit confused now. I understood that if a module returns
RLM_MODULE_FAIL that radiusd would not return an authorization
reject. However, it appears that it still does.
Have a look at doc/configurable-failover
--
Groeten, Regards, Salutations,
Thor Spruyt
M: +32
Doug Hardie wrote:
I am trying to get the Ascend NASs to switch to the secondary radius
server when the primary has a failure condition. I know that no
response will cause that, but haven't been able to find any way to
make the switch occur with the primary is not working properly. Is
there
Doug Hardie [EMAIL PROTECTED] wrote:
I am trying to get the Ascend NASs to switch to the secondary radius
server when the primary has a failure condition. I know that no
response will cause that, but haven't been able to find any way to
make the switch occur with the primary is not
I am a bit confused now. I understood that if a module returns
RLM_MODULE_FAIL that radiusd would not return an authorization
reject. However, it appears that it still does.
rad_recv: Access-Request packet from host 127.0.0.1:53579, id=193,
length=71
User-Name = visitor
Doug Hardie [EMAIL PROTECTED] wrote:
I am a bit confused now. I understood that if a module returns
RLM_MODULE_FAIL that radiusd would not return an authorization
reject. However, it appears that it still does.
RADIUS servers are supposed to return Access-Reject's for
Access-Accepts,
On Jul 28, 2005, at 17:09, Alan DeKok wrote:
RADIUS servers are supposed to return Access-Reject's for
Access-Accepts, rather than just dropping the packets.
If the server *requires* a back-end DB, and that DB is down, then
arguable the server can pretend it's down, too.
I am trying
Doug Hardie [EMAIL PROTECTED] wrote:
However the NASs didn't switch to the backup radius server which was
operating properly. We are trying to figure out why they didn't
switch.
When the server gives up on a thread, it sends a Reject back to the
NAS. This behaviour should probably be
7 matches
Mail list logo
