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 maybe 1.01+
second after the first request, but freeradius drops the current request
instead of the new one. Soon I'm gonna rebuild freeradius with changed
tv_sec and check that.
huh? do you not understand the basic context of this issue? if the NAS
has sent a repeat RADIUS packet then it means that the original packet
has already been timed out and the NAS should NOT accept an 'accept' response
on that original packet.
Please see the comment from the code snippet in src/main/event.c in my
original posting. Some duplicate packets might arrive after 1 sec. by a
slight margin, even though they logically are whatever that
special-cased conditional was designed to handle.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
