Hi,
>If this was a problem related to the client running out of ID REQUEST
>where can I look on the logs for a warning or something alerting that this
>is happening?
welcome to the party. in the UK we have seen this issue to - and it doesnt take
that much until the server is all backl
Hi Alan
We add to all our peers handler configurations a “NoReplyHook”
(Paul Dekkers from Surfnet is also helping us on this problem)
Host x.x.x.x
Secret
AuthPort 1812
AcctPort 1813
Retries 1
UseExtendedIds
NoReplyHook file:"/etc/radius/RejectNotIgnore.pl"
AuthLog roamingstats
Acc
Hi,
> We add to all our peers handler configurations a “NoReplyHook”
> (Paul Dekkers from Surfnet is also helping us on this problem)
okay - thats pretty much similar to what I have and recommend too :-)
one question though - what is our FarmSize set to? how many threads
are you running - and a
On 05/25/2011 01:39 PM, Esmeralda Pires wrote:
Hello Esmeralda,
> We add to all our peers handler configurations a “NoReplyHook”
> (Paul Dekkers from Surfnet is also helping us on this problem)
I have attached another version of a NoReplyHook. This is from the
Finnish eduroam root that I am also
On 05/24/2011 05:06 PM, Alexander Hartmaier wrote:
> Since changing the init script line 37 from:
> [ -z "${RADIUSD_ARGS}" ] && RADIUSD_ARGS="-config_file $RADIATOR_CONFIG
> -daemon $RADIATOR_ARGS"
> [ -z "${RADIUSD_ARGS}" ] && RADIUSD_ARGS="-config_file $RADIATOR_CONFIG
> $RADIATOR_ARGS -foregro
Hi Heikki,
no, this is only acting as tacacs+ server without any db logging.
# refresh the client list every hour
RefreshPeriod 3600
The intermediate firewalls will close the connection because the tcp
connection is inactive for about an hour.
Can we enable tcp keepalives or add a check to radia
