3 Dec
2010
3 Dec
'10
3:19 a.m.
Fabricio Viana wrote:
Let´s suppose the following situations: 1) User exists but the password is wrong 2) User does not exist
In both cases the answer is REJECT.
It happens that certain hardware is making endless attempts that eventually saturating the server.
See "reject_delay" in radiusd.conf. It's intended to slow down broken hardware.
- It is possible to cause the server, instead of rejecting the users, accept the login but responds ACCEPT with "framed-pool = pool-block" ?
Sure. Just configure that....
- Is there any way to put REJECT users in a given group by default?
See the FAQ. Alan DeKok.