Qinxue Chen <[EMAIL PROTECTED]> wrote: > The problem seems to be that the new request has the same request ID, > request code, source IP, source port, but different vectors (what's this?) It means that the request is a new one, and different from the first on. The RFC's specifically allow for this. > as one of the old requests. From the problem I saw, it is not caused by the > NAS end. The freeradius didn't clear some old requests properly in the > buffer for whatever reasons. Some request IDs stayed for about several > hours. I am not quiet sure about the whole process in the software. If Alan > or Chris could explain a little bit, it will be greatly appreciated. There's not much to say. It looks like the server has a bug. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- RE: Dropping conflicting authentication packet Qinxue Chen
- RE: Dropping conflicting authentication packet Chris Parker
- Re: Dropping conflicting authentication packet Spike Ilacqua
- Re: Dropping conflicting authentication packet Chris Parker
- RE: Dropping conflicting authentication packet Qinxue Chen
- Re: Dropping conflicting authentication packet Spike Ilacqua
- RE: Dropping conflicting authentication packet Qinxue Chen
- RE: Dropping conflicting authentication packet Chris Parker
- RE: Dropping conflicting authentication packet Qinxue Chen
- Re: Dropping conflicting authentication packet aland
- RE: Dropping conflicting authentication packet aland
- RE: Dropping conflicting authentication packet Chris Parker
- RE: Dropping conflicting authentication packet Qinxue Chen
- Re: Dropping conflicting authentication packet aland
- RE: Dropping conflicting authentication packet Qinxue Chen
- Re: Dropping conflicting authentication packet Miquel van Smoorenburg
- Re: Dropping conflicting authentication packet aland
