# The ability to change the IPv4 and IPv6 address pool will be removed
# in a future Firezone release in order to reduce the possible combinations
# of network configurations we need to handle.
Could you confirm that? Our local network reside on 100.64.0.0/10 CIDR and I suspect that this will overlap…
We deploy our custom network probe on local network of our customers: using CGNAT space and vpn allows them to contact our services backend without exposing them to internet (because the tun interface address will not overlap with customer local block); then, keeping the rest of our local network on the same space, allow us to keep internal visibility simpler (because of no NAT).
Please consider keep the possibility of using a custom IPv4 pool at least for self-hosterdscenario.