|
|
[[_TOC_]]
|
|
|
|
|
|
# Automatic Detection of Chatty Clients
|
|
|
|
|
|
A special client class called `"CHATTY"` could be implemented to be assigned to packets that are
|
|
|
automatically determined to come from the same client and to abuse the rate of packets sent.
|
|
|
|
|
|
It could be enabled by a boolean configuration entry directly under `"parameters"` called
|
|
|
`"chatty-clients-detection"` with a default of `false`, since it would incur a slight performance
|
|
|
penalty.
|
|
|
|
|
|
The client class would be assigned under the `pkt[46]_receive` hook point. It can then be lease
|
|
|
limited or rate limited.
|
|
|
|
|
|
Two packets are considered to come from the same client if they have he same hardware address or
|
|
|
client ID or a combination of both for v4, and the same DUID for v6.
|
|
|
|
|
|
A client is considered chatty if:
|
|
|
* it sent 4 or more packets in the last period equal to renew time, where at least one had the
|
|
|
requested IP address option filled which means that the client either has a valid lease or it is in
|
|
|
init-reboot state.
|
|
|
* it sent 4 or more packets in the last minute where neither of the packets had a hint.
|
|
|
|
|
|
4 is an arbitrarily chosen number. It could be configurable or hardcoded. |
|
|
\ No newline at end of file |