diff options
| author | Beniamino Galvani <bgalvani@redhat.com> | 2016-01-27 11:21:23 +0100 |
|---|---|---|
| committer | Beniamino Galvani <bgalvani@redhat.com> | 2016-02-02 15:23:34 +0100 |
| commit | 1d1a3e0afb85478cda43670b8ed92a6db6c83f3e (patch) | |
| tree | 97b240693fba36064c44c19b458031a3089f7beb /units/systemd-kexec.service.in | |
| parent | cd72d2044ad28b475bf84a38ba6db45292467dd8 (diff) | |
dhcp: delay restarts after NAKs
The server might answer to a DHCPREQUEST with a NAK and currently the
client restarts the configuration process immediately. It was
observed that this can easily generate loops in which the network is
flooded with DISCOVER,OFFER,REQUEST,NAK sequences.
RFC 2131 only states that "if the client receives a DHCPNAK message,
the client restarts the configuration process" without further
details.
Add a delay with exponential backoff between retries after NAKs to
limit the number of requests and cap the delay to 30 minutes.
Diffstat (limited to 'units/systemd-kexec.service.in')
0 files changed, 0 insertions, 0 deletions