<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div>Any network could be grouped in small networks. Physically I would imagine your example as five floor building with IOT load of 200 per floor. If each floor is its own subnet (192.168.x.x/20 gives wiggle room to adress computation in dnsmasq), then roaming
to meetings can be made seemless (some popular productivity software will hang on dhcp changes). Each subnet has its own dnsmasq instance. There are ways to ensure complete local DNS resolution of DHCP leases for ether of running an instance per subnet on
one serever, or having each in the physical router "per floor." Also to reduce insane port remapping in IPV4 NAT have all subnet dnsmaq go through one unique dnsmasq instance (max cache) for global resolution. Internal, local dnsmasq can use fixed request
ports like 1053 to keep socket limits in check.</div>
<div><br>
</div>
Eric
<div><br>
</div>
<div></div>
</body>
</html>