Sorry for bugging you, discovered that the identifyer was the same (even if the content was different). The random function that generates it (in junipers libradius) was seeded by the time in seconds which led to the same result from random in several packages if sent very quickly. /Alex

-----Original Message----- From: freeradius-devel-bounces+alexander.schrab=axis.com@lists.freer adius.org [mailto:freeradius-devel-bounces+alexander.schrab=axis.com@lis ts.freeradius.org] On Behalf Of Alexander Schrab Sent: den 27 november 2006 14:08 To: FreeRadius developers mailing list Subject: Two requests shortly after each other

Hi,

Is this some sort of anti-DoS-feature?

I send one request with a username/password pair and get a sucessfull reply. Then I send another with different username/password directly after the first one. This request should result in a different reply, but I get a duplicate of the old reply:

--------------------------------- radius_xlat: 'User' Sending Access-Accept of id 144 to 10.92.163.211 port 3079 Reply-Message = "User" Finished request 2 Going to the next request --- Walking the entire request list --- Waking up in 6 seconds... rad_recv: Access-Request packet from host 10.92.163.211:3079, id=144, length=53 Sending duplicate reply to client localhost:3079 - ID: 144 Re-sending Access-Accept of id 144 to 10.92.163.211 port 3079 Waking up in 6 seconds... ---------------------------------

/Alex

- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html