incidents: client dhcp pool maintenance
This commit is contained in:
parent
f01e35c531
commit
ddb00c61ff
|
@ -120,3 +120,17 @@ I ran ansible with `--fork=1` to update on ap at a time (every ap takes about 5
|
||||||
**impact**:
|
**impact**:
|
||||||
Either clients "roamed" (no fast roaming - short interuptions) to a different ap or waited till the original ap came back online.
|
Either clients "roamed" (no fast roaming - short interuptions) to a different ap or waited till the original ap came back online.
|
||||||
For every client not more than 10-15 seconds service interruption.
|
For every client not more than 10-15 seconds service interruption.
|
||||||
|
|
||||||
|
|
||||||
|
2022.07.17 01:50 | (maintenance) increase dhcp pool size for clients
|
||||||
|
--------------------------------------------------------------------
|
||||||
|
|
||||||
|
The dnsmasq instance for the client network (`10.84.4.0/22`) only used the dhcp pool `10.84.4.100 - .250`.
|
||||||
|
|
||||||
|
To be able to actually assign the full `/22` to clients I've changed the pool to `10.84.4.2 - 10.84.7.254`.
|
||||||
|
|
||||||
|
Afterwards I've reloaded `dnsmasq` on `gw-core01`.
|
||||||
|
|
||||||
|
**impact**: none
|
||||||
|
|
||||||
|
Currently `dnsmasq` has handed out 104 leases, so we presumably never ran out of ips in the old pool.
|
||||||
|
|
Reference in New Issue