On 07/07/2011 12:28 PM, Alexander Clouter wrote:
rihadri...@mail.ru wrote:
Hi, all. We have some legacy software that ran under XTradius
(xtradius.sourceforge.net). The important thing was to execute an
external program for every auth accounting request. Now I need to
recreate all that on
Hi, all. We have some legacy software that ran under XTradius
(xtradius.sourceforge.net). The important thing was to execute an
external program for every auth accounting request. Now I need to
recreate all that on another server, and I must use the same legacy
billing software. Unfortunately
Hi,
We have FreeRADIUS 2.1.3 servicing four Cisco NASses, which in turn
service hundreds of PPPoE clients. rlm_perl with a custom written script
is used for authorization/accounting, performing at about 10 auth
requests/sec on a Dell PowerEdge 2950 box. At times, when a NAS is
rebooted,
Alan DeKok wrote:
However, if you want to work around the problem, set max_requests
to something like 128000. The server will use more RAM, but it will
make progress.
But I'm not seeing this line at times requiring operator interference:
Info: WARNING: Please check the configuration file.
Alan Buxey wrote:
Hi,
Our radius-server timeout is high enough: 4 minutes. Once again: I
suppose that what freeradius thinks of as Received conflicting packet
... are rather a bit delayed packets normally treated as Discarding
conflicting packet ..., i.e. they arrive at freeradius in
Ivan Kalik wrote:
Our radius-server timeout is high enough: 4 minutes. Once again: I
suppose that what freeradius thinks of as Received conflicting packet
... are rather a bit delayed packets normally treated as Discarding
conflicting packet ..., i.e. they arrive at freeradius in maybe 1.01+
Alan DeKok wrote:
rihad wrote:
Trying for the third time:
Do you have any intention of reading the messages here?
there are many, many requests of the
Discarding conflicting packet kind, which for one reason or another
are dupped by our Cisco NASes in under one second (see the code
Alan DeKok wrote:
rihad wrote:
Oh yeah? Isn't Cisco 7260 good enough for you?
Q: Hi, I have a RADIUS server that is slower than a 386, and a NAS that
violates the RADIUS protocol. What should I do?
A: Fix the server and the NAS.
Q: You bastards! How dare you tell me my equipment
Ivan Kalik wrote:
Being 100% correct protocol-wise means nothing, if the software can't
fit well into an environment.
Exactly. The only problem being your inability to comprehend that
freeradius is not faulty but it is your perl script that can't cope.
Why do you not understand that even if I
Hi, all,
Sometimes when there are too many requests from a NAS, like right after
rebooting it and thus breaking current sessions, etc., freeradius 2.1.3
under FreeBSD begins loggin many many lines like this after the NAS
re-sends unanswered packets:
Error: Received conflicting packet from
Alan DeKok wrote:
but aborting the current packet instead of
the new duplicate one can hardly be justified.
Nonsense. The duplicate one is an indication that the *NAS* has given
up on the first packet. Spending more time processing the current
packet is useless, because the NAS will ignore
Ivan Kalik wrote:
That is, not many (if any) of our Receved ... lines are due to what
could be considered a NAS timeout, and they should be treated like
Discarding ..., that is, the new request should be dropped.
No, NAS qouldn't wait on your script to finish so it gave up and has tried
again
12 matches
Mail list logo
