Hi,
I've just downloaded,compiled and installed the latest version of 2.2 (2.2.1?)
from git.freeradius.org.
Installed it on an internal server and things seemed to work o.k. I then
upgraded another server that deals with our external ( eduroam) connectivity
and within a few mins am seeing
On 07.03.2013 11:32, Alex Sharaz wrote:
Hi,
I've just downloaded,compiled and installed the latest version of 2.2 (2.2.1?)
from git.freeradius.org.
Installed it on an internal server and things seemed to work o.k. I then
upgraded another server that deals with our external ( eduroam)
Though you might say that. Running FR in debug mode now
A
On 7 Mar 2013, at 11:18, Olivier Beytrison oliv...@heliosnet.org wrote:
On 07.03.2013 11:32, Alex Sharaz wrote:
Hi,
I've just downloaded,compiled and installed the latest version of 2.2
(2.2.1?) from git.freeradius.org.
Installed
Hi,
The server is basically proxying off auth requests to remote RADIUS servers.
Is the above just telling me that the other end is taking a while to reply or
is there some underlying issue?
what is your retry time set to on the NAS kit? If your kit is expecting
a reply in eg 3
On 7 Mar 2013, at 11:36, a.l.m.bu...@lboro.ac.uk wrote:
Hi,
The server is basically proxying off auth requests to remote RADIUS servers.
Is the above just telling me that the other end is taking a while to reply
or is there some underlying issue?
what is your retry time set to on the
Hi,
response_window = 5
thats a little low. the default provided with FreeRADIUS is 20 IIRC - and
you need to ensure that theres correlation with the NAS
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 7 Mar 2013, at 12:15, a.l.m.bu...@lboro.ac.uk wrote:
Hi,
response_window = 5
thats a little low. the default provided with FreeRADIUS is 20 IIRC - and
you need to ensure that theres correlation with the NAS
o.k can't remember where I got that value, suspect it was
On 7 Mar 2013, at 06:21, Alex Sharaz alex.sha...@york.ac.uk wrote:
Though you might say that. Running FR in debug mode now
A
If you can't reproduce it with -X, try with the -fxxl stdout incantation, -X
will also force the server into single threaded mode, and this might be a
locking issue.
Thanks for your response, Alan.
On 2/9/10 4:01 AM, Alan DeKok wrote:
The message was *changed* in that commit:
So it was previously there... My upgrade was from version 2.1.6, and
don't remember to have seen it before, but I'll check...
The message is generated when the child thread
Hi,
I have upgraded recently one of my servers to 2.1.8 (RHEL 5), and am
seeing thousands of messages like this in a day. It looks the message
was introduced with patch no. 139c45b4c51c945414b53ece36bbeb42edb1b2a7
from November 29.
I'm wondering what parameters should I tune to get these
José Manuel wrote:
I have upgraded recently one of my servers to 2.1.8 (RHEL 5), and am
seeing thousands of messages like this in a day. It looks the message
was introduced with patch no. 139c45b4c51c945414b53ece36bbeb42edb1b2a7
from November 29.
The message was *changed* in that commit:
11 matches
Mail list logo
