> > No. Read the RFC. Understand how Authentication-Vector is > used. Your > case1 is correct, your case2 is handled. > > The reason there is a problem is old requests are for some reason not > being cleared. That's all there is, don't try and make it > more complex, > it's a bug in the code, not a design flaw. > No matter how smoothly the code can run, case1 should be always considered from the design point of view. Then the two cases need to be identified. That's what I thought. --Qinxue Chen __________________________________________ NetZero Platinum Sign Up Today - Only $9.95 per month! http://www.netzero.net - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- 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
