> Once upon a time Stephen Fisher shaped the electrons to say...
> >Sun Nov 24 18:49:03 1996: Dropping duplicate: from pm3.cia-g.com - ID: 209
>
> The PM is sending a request and not hearing back in time. But RADIUS got
> it. So by the time the PM gets the reply it has sent multiple requests.
> Since RADIUS saw it and dealt with it, it drops the duplicate requests.
Aah..
> >That PM2eR is running ComOS 3.3.3 as are my other two PM's (which work
> >fine with Radius 2.0). The only difference is that only PM3 is a remote
> >POP, the other two are on the same ethernet as the radius server. It
>
> Being on a remote POP could be the issue. If the link is saturated it
> would cause a delay. It could also be a routing issue.
>
> I don't suspect RADIUS because if the server was too slow it would be too
> slow for ALL 3 PMs.
Yeah, the POP has ~42ms ping rates (2 hops away) to it while the local
ones have ~0.7ms.. How would I slow it down so it doesn't give up so
quickly?
I just downloaded the Radius 2.0 source code and compiled it and got the
same results as the precompiled binary.
Ergh, I ran into this problem before after switching to Radius 2.0 once
before and had to switch back to 1.16, I can't do that right now. Does
anyone have any ideas??
Thanx..
- Steve
- Systems Manager
- Community Internet Access, Inc.
- Gallup and Grants, New Mexico