comunication between different locations with same subnet #1588

Open
opened 2025-11-20 05:33:21 -05:00 by saavagebueno · 2 comments
Owner

Originally created by @AlbSrd on GitHub (Jan 31, 2025).

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). 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)

@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.

@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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1588