[GH-ISSUE #3259] comunication between different locations with same subnet #7019

Open
opened 2026-08-05 01:11:12 -04:00 by saavagebueno · 3 comments
Owner

Originally created by @AlbSrd on GitHub (Jan 31, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3259

Hello, i would like to connect my site1 with subnet 10.0.0.0/24 to my site2 (in a different city) with the same subnet 10.0.0.0/24.
I made a network linking them and a policy to allow any protocol between them.
On site1 my host with netbird is at 10.0.0.128 and on site2 the host with netbrid is at 10.0.0.135 BUT i have an host with 10.0.0.135 in site1 too....
I added them to "resources" and in "routing peer" in the network but they can't ping each other.
if i use the 100.x.x.x ip from netbird network they ping each other.
I can't change subnet in site1 or site2; how can my host in site1 know to ping the host in site2 and not the host at 10.0.0.135 in its same phisical subnet?

Originally created by @AlbSrd on GitHub (Jan 31, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3259 Hello, i would like to connect my site1 with subnet 10.0.0.0/24 to my site2 (in a different city) with the same subnet 10.0.0.0/24. I made a network linking them and a policy to allow any protocol between them. On site1 my host with netbird is at 10.0.0.128 and on site2 the host with netbrid is at 10.0.0.135 BUT i have an host with 10.0.0.135 in site1 too.... I added them to "resources" and in "routing peer" in the network but they can't ping each other. if i use the 100.x.x.x ip from netbird network they ping each other. I can't change subnet in site1 or site2; how can my host in site1 know to ping the host in site2 and not the host at 10.0.0.135 in its same phisical subnet?
Author
Owner

@1nerdyguy commented on GitHub (Jan 31, 2025):

this is a networking problem, not a Netbird problem.

You have 2 hosts with the same IP, and basically connected them. That's bad.

I'd recommend just installing the netbird client to all hosts vs using the network deployment/routes, and use the hostnames with the Netbird fqdn (or update your local dns to use it)

<!-- gh-comment-id:2628348677 --> @1nerdyguy commented on GitHub (Jan 31, 2025): this is a networking problem, not a Netbird problem. You have 2 hosts with the same IP, and basically connected them. That's bad. I'd recommend just installing the netbird client to all hosts vs using the network deployment/routes, and use the hostnames with the Netbird fqdn (or update your local dns to use it)
Author
Owner

@Strat00s commented on GitHub (Aug 16, 2025):

If NetBird peers were capable of creating 1:1 NAT, mapping their local devices to NetBird VPN and being used to route the traffic, could that be used to somewhat solve this problem? Since then, every device would have a unique address to be accessed through (the 100.64.x.x), even if it is not running the NetBird client.
I honestly have no idea if what I am saying even makes sense; networking is black magic for me.

<!-- gh-comment-id:3193772353 --> @Strat00s commented on GitHub (Aug 16, 2025): If NetBird peers were capable of creating 1:1 NAT, mapping their local devices to NetBird VPN and being used to route the traffic, could that be used to somewhat solve this problem? Since then, every device would have a unique address to be accessed through (the 100.64.x.x), even if it is not running the NetBird client. I honestly have no idea if what I am saying even makes sense; networking is black magic for me.
Author
Owner

@ZD-FLoM commented on GitHub (Nov 25, 2025):

I would expect the local PC level network interface metric to handle this.
Netbird interface metric: 1, 10.0.0.0/24 hits this interface first
Physical interface metric: 2

I think since both interfaces have the same subnet, interface with metric 2 would never get hit, which in this case is desired.

In the grand scheme of networking you would have less headaches if site1 and site2 were different and then traffic was routed between them.
site1: 10.0.0.0/24
site2: 10.1.0.0/24

Exact subnet copies sound like high availability / failover to me, at least where services are not so dynamic, not 2 different sites with different services.

<!-- gh-comment-id:3575175889 --> @ZD-FLoM commented on GitHub (Nov 25, 2025): I would expect the local PC level network interface metric to handle this. Netbird interface metric: 1, 10.0.0.0/24 hits this interface first Physical interface metric: 2 I think since both interfaces have the same subnet, interface with metric 2 would never get hit, which in this case is desired. In the grand scheme of networking you would have less headaches if site1 and site2 were different and then traffic was routed between them. site1: 10.0.0.0/24 site2: 10.1.0.0/24 Exact subnet copies sound like high availability / failover to me, at least where services are not so dynamic, not 2 different sites with different services.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#7019