SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-16 13:12:11 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Title : 1000ft How to Container-A > Container-B(netbird) >>>> Container-C(netbird) > Container-D #2062

New Issue
Closed
opened 2025-11-20 06:12:08 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 06:12:08 -05:00
Owner
Copy Link

Originally created by @ks-nss on GitHub (Jul 10, 2025).

We have the following setup....

2 Servers (On Different Clouds)
Server-1 has Container-A & B
Server-2 has Container-C & D
A+B containers are attached the a docker network and C+D containers are on a docker network, this subnet is 192.168.110.0/24
A HTTP Server runs in Container D and has the IP 192.168.110.4

Netbird runs in both Containers B + C on servers 1/2, and they can ping each other

How do I get Container-A to connect to Container-D ?
I want to be able to run "curl http://192.168.110.4" on Container-A and for it to be able to connect to the a http server on Container-D

I know if I add a network/route for the Subnet 192.168.110.0/24 and set the netbird instance on Container-C as the "peer" I can do the following.
From Container-B(netbird) I can curl and can connect to the http service on Container-D
So I am 3/4 of the way there... I just can't figure out how I get routing from Container-A to B to work...

Not sure if this is a netbird issue or a container issue, but if anyone has any advice / pointers then that would be really helpful.

Thanks

Originally created by @ks-nss on GitHub (Jul 10, 2025). We have the following setup.... 2 Servers (On Different Clouds) Server-1 has Container-A & B Server-2 has Container-C & D A+B containers are attached the a docker network and C+D containers are on a docker network, this subnet is 192.168.110.0/24 A HTTP Server runs in Container D and has the IP 192.168.110.4 Netbird runs in both Containers B + C on servers 1/2, and they can ping each other How do I get Container-A to connect to Container-D ? I want to be able to run "curl http://192.168.110.4" on Container-A and for it to be able to connect to the a http server on Container-D I know if I add a network/route for the Subnet 192.168.110.0/24 and set the netbird instance on Container-C as the "peer" I can do the following. From Container-B(netbird) I can curl and can connect to the http service on Container-D So I am 3/4 of the way there... I just can't figure out how I get routing from Container-A to B to work... Not sure if this is a netbird issue or a container issue, but if anyone has any advice / pointers then that would be really helpful. Thanks
saavagebueno added the questionnetworking labels 2025-11-20 06:12:08 -05:00
saavagebueno commented 2025-11-20 06:12:09 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Jul 10, 2025):

This seems to be a site-to-site use case (Server 1/2 being sites), NetBird-wise you'd do something like:

  • create Network Route 1:
    • routed through Container B
    • handling Server 1's Docker network range
    • advertised to Container C
  • create Network Route 2:
    • routed through Container C
    • handling Server 2's Docker network range
    • advertised to Container B

Then, within the respective Docker networks (aka sites) you need to somehow set up the rules to:

  • on Server 1's Docker network/Container A to route Server 2's docker ip range through Container B
  • on Server 2's Docker network/Container D to router Server 1's docker ip range through Container C

This seems to be docker-specific question, I am not sure how to achieve it within Docker, but you might have some luck setting up the routes on the hosts (Server 1/2) instead of within the container. That would make Server 2's network accessible to everything on Server 1, but should work.

@nazarewk commented on GitHub (Jul 10, 2025): This seems to be a site-to-site use case (Server 1/2 being sites), NetBird-wise you'd do something like: - create Network Route 1: - routed through Container B - handling Server 1's Docker network range - advertised to Container C - create Network Route 2: - routed through Container C - handling Server 2's Docker network range - advertised to Container B Then, within the respective Docker networks (aka sites) you need to somehow set up the rules to: - on Server 1's Docker network/Container A to route Server 2's docker ip range through Container B - on Server 2's Docker network/Container D to router Server 1's docker ip range through Container C This seems to be docker-specific question, I am not sure how to achieve it within Docker, but you might have **some** luck setting up the routes on the hosts (Server 1/2) instead of within the container. That would make Server 2's network accessible to everything on Server 1, but should work.
saavagebueno commented 2025-11-20 06:12:09 -05:00
Author
Owner
Copy Link

@ks-nss commented on GitHub (Jul 10, 2025):

Thanks for the reply @nazarewk. I think your right this is more of a docker issue than a Netbird one. I don't really know how Netbird works but I was hoping I could someone get one "central" Netbird instance in a container on a server, and somehow get other containers to magically send their traffic via that one Netbird container.

Having thought a bit more about this, I now think I want each of my containers to have their own Netbird (sidecar?). So I will close this issue and open another one.

@ks-nss commented on GitHub (Jul 10, 2025): Thanks for the reply @nazarewk. I think your right this is more of a docker issue than a Netbird one. I don't really know how Netbird works but I was hoping I could someone get one "central" Netbird instance in a container on a server, and somehow get other containers to magically send their traffic via that one Netbird container. Having thought a bit more about this, I now think I want each of my containers to have their own Netbird (sidecar?). So I will close this issue and open another one.
saavagebueno commented 2025-11-20 06:12:09 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Jul 11, 2025):

@ks-nss you could always run the NetBird container with host networking for the IP-based connectivity to work. I am not 100% sure if/how to integrate the DNS there, though.

@nazarewk commented on GitHub (Jul 11, 2025): @ks-nss you could always run the NetBird container with host networking for the IP-based connectivity to work. I am not 100% sure if/how to integrate the DNS there, though.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label networking question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2062
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?