mirror of
https://github.com/vmstan/gravity-sync.git
synced 2025-07-09 02:34:06 -04:00
Updated DHCP Replication (markdown)
parent
102b252f1d
commit
3c1a54ff23
@ -8,16 +8,16 @@ You will need to think about how to lay out your DHCP assignments before using r
|
||||
|
||||
For the sake of explanation, we'll use a standard class C subnet that can be found in most home or small business networks.
|
||||
|
||||
Subnet: `192.168.1.0/24`
|
||||
Router: `192.168.1.1`
|
||||
DNS 1: `192.168.1.10`
|
||||
DNS 2: `192.168.1.20`
|
||||
* Subnet: `192.168.1.0/24`
|
||||
* Router: `192.168.1.1`
|
||||
* DNS 1: `192.168.1.10`
|
||||
* DNS 2: `192.168.1.20`
|
||||
|
||||
The network has around 50 devices on it that need IP addresses. We'll breakup the network into a shared scope that both Pi-hole can assign static DHCP addresses from, and then each Pi-hole will have their own scopes.
|
||||
|
||||
Shared Scope: `192.168.1.50-192.168.1.99`
|
||||
Split Scope 1: `192.168.1.100-192.168.1.149`
|
||||
Split Scope 2: `192.168.1.150-192.168.1.199`
|
||||
* Shared Scope: `192.168.1.50-192.168.1.99`
|
||||
* Split Scope 1: `192.168.1.100-192.168.1.149`
|
||||
* Split Scope 2: `192.168.1.150-192.168.1.199`
|
||||
|
||||
## Shared Scope
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user