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
Hi all,
I have been asking this in October 2008, while using 2.0.4
FR is eating Memory and I do not know how to troubleshoot this.
It takes about 1 MB/ Minute which was about 3.5 GB over
some Days, before we
rcognized this.
Alan: There were issues with older versions of the
rihad wrote:
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
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
rihad wrote:
Absurd. The Dell PowerEdge 2950 w/ 2 quad-cores cannot itself without
human intervention survive the NAS attack exactly due to having to
give up on hundreds of requests per second
Your dual quad-core box can't handle hundreds of packets a second?
Wow... your Perl script is
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
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
7 matches
Mail list logo
