Is there a way to ensure just the DHCP range is not Synched

[pablo07928]

I have a 2 pihole setup where one is distributing IPs on 192.168.1.2-192.168.1.10 and the other in 192.168.1.11 -192.168.1.20 . The rest of my computers have static leases on 192.168.1.50-192.168.1.255

I would like to replicate the static lease but exclude the DHCP range replication. Is it there a way to use the exclude filters for such a setup?

[lovelaze]

Hi @pablo07928

Should be possible - I haven't tried this but you should be able to do something like this with the selective sync mode:

FULL_SYNC=false
...
SYNC_GRAVITY_DHCP_LEASES=true
SYNC_CONFIG_DHCP=true
SYNC_CONFIG_DHCP_EXCLUDE=start,end

[pablo07928]

I have tried this before and It does not work. If I do the sync It does change the Ip address. Who can confirm this is acutally implemented, or is it a possible bug?

[lovelaze]

What version are you running?

Can you elaborate on what is not working?

[pablo07928]

Pihole Version Core [v6.1.4]FTL [v6.2.3]

this is my docker confing:
services:
nebula-sync:
image: ghcr.io/lovelaze/nebula-sync:latest
container_name: Pihole-10to20
environment:
- TZ=America/New_York # Replace with your desired timezone
- PRIMARY=http://10.0.1.10|pass
- REPLICAS=http://10.0.1.11|pass
- FULL_SYNC=false
- CLIENT_RETRY_DELAY_SECONDS=15
- CLIENT_TIMEOUT_SECONDS=45
- SYNC_CONFIG_DNS=false
- SYNC_CONFIG_DHCP=true
- SYNC_CONFIG_DHCP_EXCLUDE=start,end
- SYNC_CONFIG_NTP=false
- SYNC_CONFIG_RESOLVER=false
- SYNC_CONFIG_DATABASE=false
- SYNC_CONFIG_MISC=false
- SYNC_CONFIG_DEBUG=false
- SYNC_GRAVITY_DHCP_LEASES=true
- SYNC_GRAVITY_GROUP=false
- SYNC_GRAVITY_AD_LIST=false
- SYNC_GRAVITY_AD_LIST_BY_GROUP=false
- SYNC_GRAVITY_DOMAIN_LIST=false
- SYNC_GRAVITY_DOMAIN_LIST_BY_GROUP=false
- SYNC_GRAVITY_CLIENT=false
- SYNC_GRAVITY_CLIENT_BY_GROUP=false
- RUN_GRAVITY=true
- SYNC_CONFIG_DHCP_EXCLUDE=subnet
- CRON=0 * * * *
networks: {}

If I have my dhcp scope on pihole 1 to 10.0.1.20-10.0.1.30 and on pihole 2 to 10.0.1.31-10.0.1.40 and I run nebulasync : Latest then both dhcp scopers become 10.0.1.20-10.0.1.3 so it is not excluding Start, end even if it is in the config