LAN to LAN traffic between peers not working #2150

Open
opened 2025-11-20 07:04:48 -05:00 by saavagebueno · 4 comments
Owner

Originally created by @Ignattious on GitHub (Aug 4, 2025).

Describe the problem

2 Peers

Netbird A
Netbird B

Each peer / site has 1 LAN attached:
A 10.1.100.0/24
B 10.1.101.0/24

Can ping between:

Netbird Peer Site A to LAN B (Using Netbird 100.190.x.x source)
Netbird Peer Site B to LAN A (Using Netbird 100.190.x.x source)

Cannot Ping from Peer A LAN to Peer B LAN (Using LAN IP source)
Cannot Ping from Peer B LAN to Peer A LAN (Using LAN IP source)

To Reproduce

Add 2 Peers
Add Resources
Add Resource to Routing Peer

Expected behavior

Should be able to route between LAN networks using 2 ore more routing peers

Self Hosted
netbird version 0.52.2
No Other VPN software

Can see packets going over wt0 tunnel but get dropped on routing peer before going into LAN network, If the source is a netbird 100.190.x.x address from either end packets are transferred normally.

Policy should be allowed to be created to allow LAN networks from 2 different peers to communicate. In some cases, it is impossible to install netbird on all machines and we must rely on routing peers to provide communication between 2 different networks

Tailscale has similar functionality:

https://tailscale.com/kb/1214/site-to-site

Originally created by @Ignattious on GitHub (Aug 4, 2025). **Describe the problem** 2 Peers Netbird A Netbird B Each peer / site has 1 LAN attached: A 10.1.100.0/24 B 10.1.101.0/24 Can ping between: Netbird Peer Site A to LAN B (Using Netbird 100.190.x.x source) Netbird Peer Site B to LAN A (Using Netbird 100.190.x.x source) Cannot Ping from Peer A LAN to Peer B LAN (Using LAN IP source) Cannot Ping from Peer B LAN to Peer A LAN (Using LAN IP source) **To Reproduce** Add 2 Peers Add Resources Add Resource to Routing Peer **Expected behavior** Should be able to route between LAN networks using 2 ore more routing peers Self Hosted netbird version 0.52.2 No Other VPN software Can see packets going over wt0 tunnel but get dropped on routing peer before going into LAN network, If the source is a netbird 100.190.x.x address from either end packets are transferred normally. Policy should be allowed to be created to allow LAN networks from 2 different peers to communicate. In some cases, it is impossible to install netbird on all machines and we must rely on routing peers to provide communication between 2 different networks Tailscale has similar functionality: https://tailscale.com/kb/1214/site-to-site
saavagebueno added the triage-needed label 2025-11-20 07:04:48 -05:00
Author
Owner

@1nerdyguy commented on GitHub (Aug 4, 2025):

Netbird, to my knowledge, does not have this feature. You can publish a site to a client/group of clients, but not a site to site.

@1nerdyguy commented on GitHub (Aug 4, 2025): Netbird, to my knowledge, does not have this feature. You can publish a site to a client/group of clients, but not a site to site.
Author
Owner

@stildalf commented on GitHub (Aug 7, 2025):

@Ignattious ,

Out of interest, are your A & B peers also the gateways for their relevant LANs?
(such as pfSense/OPNsense perhaps)

@stildalf commented on GitHub (Aug 7, 2025): @Ignattious , Out of interest, are your A & B peers also the gateways for their relevant LANs? (such as pfSense/OPNsense perhaps)
Author
Owner

@nadieaqui commented on GitHub (Aug 7, 2025):

@Ignattious ,

Out of interest, are your A & B peers also the gateways for their relevant LANs? (such as pfSense/OPNsense perhaps)

@stildalf , I have the same problem, and A & B are the gateways for their relevant LANs for my scenario. Any insight would be appreciated. thank you.

@nadieaqui commented on GitHub (Aug 7, 2025): > [@Ignattious](https://github.com/Ignattious) , > > Out of interest, are your A & B peers also the gateways for their relevant LANs? (such as pfSense/OPNsense perhaps) @stildalf , I have the same problem, and A & B are the gateways for their relevant LANs for my scenario. Any insight would be appreciated. thank you.
Author
Owner

@fre4ki commented on GitHub (Aug 7, 2025):

You have to set a static route on your default router for the other side and route it to your local netbird router.

i never tested this but for my understanding this should work.

Edit: but when i think about that, this is not the concept of ZTNA. How should policies checked when the user are unknown.

@fre4ki commented on GitHub (Aug 7, 2025): You have to set a static route on your default router for the other side and route it to your local netbird router. i never tested this but for my understanding this should work. Edit: but when i think about that, this is not the concept of ZTNA. How should policies checked when the user are unknown.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2150