SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-06-10 17:31:53 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Possible Network Routes Conflict #566

New Issue
Open
opened 2025-11-20 05:13:55 -05:00 by saavagebueno · 16 comments
saavagebueno commented 2025-11-20 05:13:55 -05:00
Owner
Copy Link

Originally created by @werlitong on GitHub (Jan 1, 2024).

Describe the problem
Seems to be a routing conflict that cause network issues.
I was testing netbird and saw that after add a route to 192.168.1.0/24 i've lost access to all my internal network, only gateway (my ubiquiti's router) is accessible. So, i changed from my WiFi to 5G/4G and i surprisingly recover the access. The problem wont occour if i change the route to target a specific resource in my network or if i just disable the route in netbird dashboard.

To Reproduce
Steps to reproduce the behavior:

  1. Create a network route for all of your internal network subnet (masquerade enable and metric set to 9999)
  2. Try to access any resource excluding the gateway.

Expected behavior
I think that the expected behavior should be routes beeing created following a priority distance. I'm not sure.

Screenshots
Screenshots of command netstat -rn
Route to 192.168.1.0/24:
image

Route to 192.168.1.240/32:
image

Originally created by @werlitong on GitHub (Jan 1, 2024). **Describe the problem** Seems to be a routing conflict that cause network issues. I was testing netbird and saw that after add a route to 192.168.1.0/24 i've lost access to all my internal network, only gateway (my ubiquiti's router) is accessible. So, i changed from my WiFi to 5G/4G and i surprisingly recover the access. The problem wont occour if i change the route to target a specific resource in my network or if i just disable the route in netbird dashboard. **To Reproduce** Steps to reproduce the behavior: 1. Create a network route for all of your internal network subnet (masquerade enable and metric set to 9999) 2. Try to access any resource excluding the gateway. **Expected behavior** I think that the expected behavior should be routes beeing created following a priority distance. I'm not sure. **Screenshots** Screenshots of command `netstat -rn` Route to 192.168.1.0/24: <img width="806" alt="image" src="https://github.com/netbirdio/netbird/assets/10401181/6efbfdac-635b-4225-b4eb-a23f8ec45646"> Route to 192.168.1.240/32: <img width="787" alt="image" src="https://github.com/netbirdio/netbird/assets/10401181/77f76140-b907-4035-93e3-e19d5f3a9cbc">
saavagebueno added the bugclientroutes labels 2025-11-20 05:13:55 -05:00
saavagebueno commented 2025-11-20 05:13:56 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jan 2, 2024):

Hello @werlitong, can you confirm that your computer's local network is 192.168.1.0/24? I am not seeing the local reference for it pointing to your local network interface:

e.g., at my place, the network is 192.168.178.0/24:
image

The NetBird agent looks for this network when adding the configured route in your system's routing table. So if it is missing, that check won't find it and will think it is ok to add the incoming route.

@mlsmaycon commented on GitHub (Jan 2, 2024): Hello @werlitong, can you confirm that your computer's local network is 192.168.1.0/24? I am not seeing the local reference for it pointing to your local network interface: e.g., at my place, the network is 192.168.178.0/24: <img width="505" alt="image" src="https://github.com/netbirdio/netbird/assets/7747744/337da69c-9f67-4686-a1ad-1cb60271a52d"> The NetBird agent looks for this network when adding the configured route in your system's routing table. So if it is missing, that check won't find it and will think it is ok to add the incoming route.
saavagebueno commented 2025-11-20 05:13:56 -05:00
Author
Owner
Copy Link

@werlitong commented on GitHub (Jan 2, 2024):

Yes, subnet its correct. Maybe that's the point, check the first screenshot (first post), seems like netbird replace de route from my system if there is a route to the hole subnet /24. In other words if i put my home subnet in netbird and try to access a resource with netbird up and running using my local wifi it will cause the issue.

1.Running the command with netbird disabled:
image
image

2.Running the command with netbird route to a specific host in the network:
image
image

3.Running the command with netbird route to the hole subnet /24:
image
image

@werlitong commented on GitHub (Jan 2, 2024): Yes, subnet its correct. Maybe that's the point, check the first screenshot (first post), seems like netbird replace de route from my system if there is a route to the hole subnet /24. In other words if i put my home subnet in netbird and try to access a resource with netbird up and running using my local wifi it will cause the issue. 1.Running the command with netbird disabled: ![image](https://github.com/netbirdio/netbird/assets/10401181/2697d5a4-8ea9-4656-953d-167bc0a4c757) <img width="672" alt="image" src="https://github.com/netbirdio/netbird/assets/10401181/c0ac8bf8-15e2-4a37-9fd7-c2854dae6ada"> 2.Running the command with netbird route to a specific host in the network: ![image](https://github.com/netbirdio/netbird/assets/10401181/9e014fec-a7eb-4e41-b247-87f1aef84a66) <img width="671" alt="image" src="https://github.com/netbirdio/netbird/assets/10401181/d0f5f144-0fc4-45f0-bf86-57c9ad99eebf"> 3.Running the command with netbird route to the hole subnet /24: <img width="783" alt="image" src="https://github.com/netbirdio/netbird/assets/10401181/da52f792-554e-402e-8f6f-ca3c42e835e3"> <img width="720" alt="image" src="https://github.com/netbirdio/netbird/assets/10401181/817ad4d4-f185-4b1c-9643-efcf1c7c77e5">
saavagebueno commented 2025-11-20 05:13:56 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jan 2, 2024):

Thanks, @werlitong. We will investigate more as I cannot reproduce the case locally.

@mlsmaycon commented on GitHub (Jan 2, 2024): Thanks, @werlitong. We will investigate more as I cannot reproduce the case locally.
saavagebueno commented 2025-11-20 05:13:56 -05:00
Author
Owner
Copy Link

@werlitong commented on GitHub (Jan 2, 2024):

Sure thing! If there's any other test, i'll be happy to help! Thanks!!

@werlitong commented on GitHub (Jan 2, 2024): Sure thing! If there's any other test, i'll be happy to help! Thanks!!
saavagebueno commented 2025-11-20 05:13:57 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jan 2, 2024):

Actually, it would be great if you could create a route like this:

sudo route add 8.8.0.0/16 192.168.1.1

And then do the same checks again you did with your local net.

@mlsmaycon commented on GitHub (Jan 2, 2024): Actually, it would be great if you could create a route like this: ```shell sudo route add 8.8.0.0/16 192.168.1.1 ``` And then do the same checks again you did with your local net.
saavagebueno commented 2025-11-20 05:13:57 -05:00
Author
Owner
Copy Link

@werlitong commented on GitHub (Jan 2, 2024):

Here it is:

image image image
@werlitong commented on GitHub (Jan 2, 2024): Here it is: <img width="799" alt="image" src="https://github.com/netbirdio/netbird/assets/10401181/0600373d-57a8-4d54-bd86-146c33ed3847"> <img width="684" alt="image" src="https://github.com/netbirdio/netbird/assets/10401181/0c8e0316-f958-403a-b7a7-d3a5a952111c"> <img width="689" alt="image" src="https://github.com/netbirdio/netbird/assets/10401181/4bcdb724-8df1-4ff3-92f4-5ffd785ba631">
saavagebueno commented 2025-11-20 05:13:57 -05:00
Author
Owner
Copy Link

@werlitong commented on GitHub (Jan 19, 2024):

@mlsmaycon just test the new version 0.25.4 and problem seems to be fixed. Thank you!

@werlitong commented on GitHub (Jan 19, 2024): @mlsmaycon just test the new version 0.25.4 and problem seems to be fixed. Thank you!
saavagebueno commented 2025-11-20 05:13:57 -05:00
Author
Owner
Copy Link

@werlitong commented on GitHub (Feb 17, 2024):

i've just saw that problem still occur, i thought that was solved but recently experienced the issue again.

@werlitong commented on GitHub (Feb 17, 2024): i've just saw that problem still occur, i thought that was solved but recently experienced the issue again.
saavagebueno commented 2025-11-20 05:13:57 -05:00
Author
Owner
Copy Link

@fti7 commented on GitHub (Feb 28, 2024):

I have the same issue on a Windows Client. Netbird 0.26.2. Windows 10

On a freshly booted System (Route disabled in Netbird) i have an local route to my local Subnet.

When i enable the Route in Netbird. Nothing changes (Good, because local route already exists)

When i disable it again. Netbird delete the complete local route (Is there a Check Missing to only remove Routes with a Netbird GW?)
When i enable it again. It adds a new Route with a Netbird Peer -> All Hosts in my Subnet are unreachable

@fti7 commented on GitHub (Feb 28, 2024): I have the same issue on a Windows Client. Netbird 0.26.2. Windows 10 On a freshly booted System (Route disabled in Netbird) i have an local route to my local Subnet. When i enable the Route in Netbird. Nothing changes (Good, because local route already exists) When i disable it again. Netbird delete the complete local route (Is there a Check Missing to only remove Routes with a Netbird GW?) When i enable it again. It adds a new Route with a Netbird Peer -> All Hosts in my Subnet are unreachable
saavagebueno commented 2025-11-20 05:13:57 -05:00
Author
Owner
Copy Link

@guiguan commented on GitHub (Apr 12, 2024):

same here. Netbird will remove the local route with matching CIDR, and re-add Netbird one when reconnecting. This makes the local route unusable. Please only remove the route with Netbird gateway

@guiguan commented on GitHub (Apr 12, 2024): same here. Netbird will remove the local route with matching CIDR, and re-add Netbird one when reconnecting. This makes the local route unusable. Please only remove the route with Netbird gateway
saavagebueno commented 2025-11-20 05:13:58 -05:00
Author
Owner
Copy Link

@fti7 commented on GitHub (Apr 26, 2024):

@mlsmaycon any update on this? can you reproduce this now? thanks

@fti7 commented on GitHub (Apr 26, 2024): @mlsmaycon any update on this? can you reproduce this now? thanks
saavagebueno commented 2025-11-20 05:13:58 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Apr 26, 2024):

Hello, folks; we will work on this in the coming weeks. It should be in 0.28.0

@mlsmaycon commented on GitHub (Apr 26, 2024): Hello, folks; we will work on this in the coming weeks. It should be in 0.28.0
saavagebueno commented 2025-11-20 05:13:58 -05:00
Author
Owner
Copy Link

@fti7 commented on GitHub (Jul 14, 2024):

Hello, folks; we will work on this in the coming weeks. It should be in 0.28.0

any update on this? is it already fixed?

@fti7 commented on GitHub (Jul 14, 2024): > Hello, folks; we will work on this in the coming weeks. It should be in 0.28.0 any update on this? is it already fixed?
saavagebueno commented 2025-11-20 05:13:58 -05:00
Author
Owner
Copy Link

@captainnx commented on GitHub (Sep 29, 2024):

it not fix now

@captainnx commented on GitHub (Sep 29, 2024): it not fix now
saavagebueno commented 2025-11-20 05:13:58 -05:00
Author
Owner
Copy Link

@sofmeright commented on GitHub (Feb 3, 2025):

Is this still an issue? I think I am affected by this....

@sofmeright commented on GitHub (Feb 3, 2025): Is this still an issue? I think I am affected by this....
saavagebueno commented 2025-11-20 05:13:58 -05:00
Author
Owner
Copy Link

@MichaelUray commented on GitHub (Jul 26, 2025):

I think I have the same problem,
Windows 10 22H2,
Netbird v0.51.2,
the Netbird client creates a route with the peers local LAN IP address 192.168.0.243.

192.168.0.243 255.255.255.255 192.168.91.254 192.168.91.220 26

Why does it create in general a route to the peers LAN IP?
That should not happen in my opinion since multiple peers could have the same IP address.
All the traffic should go via the internal Netbird peer IP addresses (100.87.116.158) if peers get accessed.

The worst thing is, that it creates the route to the LAN interface (192.168.91.220) of the client instead of the Netbird interface (100.87.118.192).

At the beginn after the connect the route shows up and disappers a couple times which is weird too.

Windows Routing Table 
route print -4
===========================================================================
Schnittstellenliste
 10...2c f0 5d 36 a4 30 ......Realtek PCIe 2.5GbE Family Controller
 84...........................WireGuard Tunnel
  6...2c f0 5d 36 a4 2f ......Hyper-V Virtual Ethernet Adapter #2
 86...........................CTB VPN (IPsec)
  9...00 ff 55 bb c0 6b ......TAP-Windows Adapter V9
 15...00 ff 82 52 ec 13 ......TAP-Windows Adapter V9 #2
 17...00 ff 86 7b 57 13 ......TAP-Windows Adapter V9 #3
 12...........................OpenVPN Data Channel Offload
 27...5c a6 e6 48 c9 f5 ......TP-Link Wireless USB Adapter
 14...5e a6 e6 48 c9 f5 ......Microsoft Wi-Fi Direct Virtual Adapter
  5...5c a6 e6 48 c9 f5 ......Microsoft Wi-Fi Direct Virtual Adapter #2
 22...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1
  4...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8
  1...........................Software Loopback Interface 1
 46...00 15 5d 28 33 a6 ......Hyper-V Virtual Ethernet Adapter
===========================================================================

IPv4-Routentabelle
===========================================================================
Aktive Routen:
     Netzwerkziel    Netzwerkmaske          Gateway    Schnittstelle Metrik
          0.0.0.0          0.0.0.0   192.168.91.254   192.168.91.220    281
       10.1.233.0    255.255.255.0   Auf Verbindung    100.87.118.192      6
     10.1.233.255  255.255.255.255   Auf Verbindung    100.87.118.192    261
       10.1.238.0    255.255.255.0   Auf Verbindung    100.87.118.192      6
     10.1.238.255  255.255.255.255   Auf Verbindung    100.87.118.192    261
      10.102.0.60  255.255.255.255   192.168.91.254   192.168.91.220     26
     10.102.0.151  255.255.255.255   192.168.91.254   192.168.91.220     26
    64.141.62.202  255.255.255.255   192.168.91.254   192.168.91.220     26
   80.120.218.226  255.255.255.255   192.168.91.254   192.168.91.220     26
     92.60.39.135  255.255.255.255   192.168.91.254   192.168.91.220     26
       100.87.0.0      255.255.0.0   Auf Verbindung    100.87.118.192    261
   100.87.118.192  255.255.255.255   Auf Verbindung    100.87.118.192    261
   100.87.255.255  255.255.255.255   Auf Verbindung    100.87.118.192    261
        127.0.0.0        255.0.0.0   Auf Verbindung         127.0.0.1    331
        127.0.0.1  255.255.255.255   Auf Verbindung         127.0.0.1    331
  127.255.255.255  255.255.255.255   Auf Verbindung         127.0.0.1    331
      169.254.0.0      255.255.0.0   Auf Verbindung     169.254.34.24    291
      169.254.0.0      255.255.0.0   Auf Verbindung   169.254.222.244    291
    169.254.34.24  255.255.255.255   Auf Verbindung     169.254.34.24    291
  169.254.222.244  255.255.255.255   Auf Verbindung   169.254.222.244    291
  169.254.255.255  255.255.255.255   Auf Verbindung     169.254.34.24    291
  169.254.255.255  255.255.255.255   Auf Verbindung   169.254.222.244    291
     172.20.144.0    255.255.240.0   Auf Verbindung      172.20.144.1   5256
     172.20.144.1  255.255.255.255   Auf Verbindung      172.20.144.1   5256
   172.20.159.255  255.255.255.255   Auf Verbindung      172.20.144.1   5256
      172.23.80.1  255.255.255.255   192.168.91.254   192.168.91.220     26
  178.183.187.197  255.255.255.255   192.168.91.254   192.168.91.220     26
      192.168.0.0    255.255.255.0    192.168.0.160    192.168.0.167     26
     192.168.0.40  255.255.255.255   192.168.91.254   192.168.91.220     26
    192.168.0.167  255.255.255.255   Auf Verbindung     192.168.0.167    281
    192.168.0.243  255.255.255.255   192.168.91.254   192.168.91.220     26
     192.168.91.0    255.255.255.0   Auf Verbindung    192.168.91.220    281
   192.168.91.220  255.255.255.255   Auf Verbindung    192.168.91.220    281
   192.168.91.255  255.255.255.255   Auf Verbindung    192.168.91.220    281
        224.0.0.0        240.0.0.0   Auf Verbindung         127.0.0.1    331
        224.0.0.0        240.0.0.0   Auf Verbindung     169.254.34.24    291
        224.0.0.0        240.0.0.0   Auf Verbindung   169.254.222.244    291
        224.0.0.0        240.0.0.0   Auf Verbindung    192.168.91.220    281
        224.0.0.0        240.0.0.0   Auf Verbindung      172.20.144.1   5256
        224.0.0.0        240.0.0.0   Auf Verbindung     192.168.0.167    281
        224.0.0.0        240.0.0.0   Auf Verbindung    100.87.118.192    261
  255.255.255.255  255.255.255.255   Auf Verbindung         127.0.0.1    331
  255.255.255.255  255.255.255.255   Auf Verbindung     169.254.34.24    291
  255.255.255.255  255.255.255.255   Auf Verbindung   169.254.222.244    291
  255.255.255.255  255.255.255.255   Auf Verbindung    192.168.91.220    281
  255.255.255.255  255.255.255.255   Auf Verbindung      172.20.144.1   5256
  255.255.255.255  255.255.255.255   Auf Verbindung     192.168.0.167    281
  255.255.255.255  255.255.255.255   Auf Verbindung    100.87.118.192    261
===========================================================================
Ständige Routen:
  Netzwerkadresse          Netzmaske  Gatewayadresse  Metrik
          0.0.0.0          0.0.0.0   192.168.91.254  Standard
          0.0.0.0          0.0.0.0   192.168.91.254     256
===========================================================================
Windows ipconfig 
ipconfig /all

Windows-IP-Konfiguration

   Hostname  . . . . . . . . . . . . : uray-mic-dh
   Primäres DNS-Suffix . . . . . . . :
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein
   DNS-Suffixsuchliste . . . . . . . : netbird.selfhosted
                                       lan.kw.uray.io
                                       mainserver.local

Unbekannter Adapter wt0:

   Verbindungsspezifisches DNS-Suffix: netbird.selfhosted
   Beschreibung. . . . . . . . . . . : WireGuard Tunnel
   Physische Adresse . . . . . . . . :
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   IPv4-Adresse  . . . . . . . . . . : 100.87.118.192(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.0.0
   Standardgateway . . . . . . . . . :
   DNS-Server  . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS über TCP/IP . . . . . . . : Aktiviert
   Suchliste für verbindungsspezifische DNS-Suffixe:
                                       netbird.selfhosted

Ethernet-Adapter vEthernet (Switch LAN):

   Verbindungsspezifisches DNS-Suffix: lan.kw.uray.io
   Beschreibung. . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
   Physische Adresse . . . . . . . . : 2C-F0-5D-36-A4-2F
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   IPv4-Adresse  . . . . . . . . . . : 192.168.91.220(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Standardgateway . . . . . . . . . : 192.168.91.254
   DNS-Server  . . . . . . . . . . . : 192.168.91.254
   NetBIOS über TCP/IP . . . . . . . : Aktiviert

PPP-Adapter CTB VPN (IPsec):

   Verbindungsspezifisches DNS-Suffix: mainserver.local
   Beschreibung. . . . . . . . . . . : CTB VPN (IPsec)
   Physische Adresse . . . . . . . . :
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   IPv4-Adresse  . . . . . . . . . . : 192.168.0.167(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.255
   Standardgateway . . . . . . . . . :
   DNS-Server  . . . . . . . . . . . : 192.168.0.32
                                       192.168.0.31
   NetBIOS über TCP/IP . . . . . . . : Aktiviert


Ethernet-Adapter VMware Network Adapter VMnet1:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
   Physische Adresse . . . . . . . . : 00-50-56-C0-00-01
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::57e4:527c:b712:897f%22(Bevorzugt)
   IPv4-Adresse (Auto. Konfiguration): 169.254.34.24(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.0.0
   Standardgateway . . . . . . . . . :
   DHCPv6-IAID . . . . . . . . . . . : 335564886
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-26-9B-5C-E4-2C-F0-5D-36-A4-2F
   DNS-Server  . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS über TCP/IP . . . . . . . : Aktiviert

Ethernet-Adapter VMware Network Adapter VMnet8:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
   Physische Adresse . . . . . . . . : 00-50-56-C0-00-08
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::a920:b9c5:6ae7:1444%4(Bevorzugt)
   IPv4-Adresse (Auto. Konfiguration): 169.254.222.244(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.0.0
   Standardgateway . . . . . . . . . :
   DHCPv6-IAID . . . . . . . . . . . : 503337046
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-26-9B-5C-E4-2C-F0-5D-36-A4-2F
   DNS-Server  . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS über TCP/IP . . . . . . . : Aktiviert

Ethernet-Adapter vEthernet (Default Switch):

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
   Physische Adresse . . . . . . . . : 00-15-5D-28-33-A6
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::ad0:9a8d:e6c5:e867%46(Bevorzugt)
   IPv4-Adresse  . . . . . . . . . . : 172.20.144.1(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.240.0
   Standardgateway . . . . . . . . . :
   DHCPv6-IAID . . . . . . . . . . . : 771757405
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-26-9B-5C-E4-2C-F0-5D-36-A4-2F
   DNS-Server  . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS über TCP/IP . . . . . . . : Aktiviert
@MichaelUray commented on GitHub (Jul 26, 2025): I think I have the same problem, Windows 10 22H2, Netbird v0.51.2, the Netbird client creates a route with the peers local LAN IP address `192.168.0.243`. `192.168.0.243 255.255.255.255 192.168.91.254 192.168.91.220 26` Why does it create in general a route to the peers LAN IP? That should not happen in my opinion since multiple peers could have the same IP address. All the traffic should go via the internal Netbird peer IP addresses (`100.87.116.158`) if peers get accessed. The worst thing is, that it creates the route to the LAN interface (`192.168.91.220`) of the client instead of the Netbird interface (`100.87.118.192`). At the beginn after the connect the route shows up and disappers a couple times which is weird too. <details> <summary>Windows Routing Table</summary> ``` route print -4 =========================================================================== Schnittstellenliste 10...2c f0 5d 36 a4 30 ......Realtek PCIe 2.5GbE Family Controller 84...........................WireGuard Tunnel 6...2c f0 5d 36 a4 2f ......Hyper-V Virtual Ethernet Adapter #2 86...........................CTB VPN (IPsec) 9...00 ff 55 bb c0 6b ......TAP-Windows Adapter V9 15...00 ff 82 52 ec 13 ......TAP-Windows Adapter V9 #2 17...00 ff 86 7b 57 13 ......TAP-Windows Adapter V9 #3 12...........................OpenVPN Data Channel Offload 27...5c a6 e6 48 c9 f5 ......TP-Link Wireless USB Adapter 14...5e a6 e6 48 c9 f5 ......Microsoft Wi-Fi Direct Virtual Adapter 5...5c a6 e6 48 c9 f5 ......Microsoft Wi-Fi Direct Virtual Adapter #2 22...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1 4...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8 1...........................Software Loopback Interface 1 46...00 15 5d 28 33 a6 ......Hyper-V Virtual Ethernet Adapter =========================================================================== IPv4-Routentabelle =========================================================================== Aktive Routen: Netzwerkziel Netzwerkmaske Gateway Schnittstelle Metrik 0.0.0.0 0.0.0.0 192.168.91.254 192.168.91.220 281 10.1.233.0 255.255.255.0 Auf Verbindung 100.87.118.192 6 10.1.233.255 255.255.255.255 Auf Verbindung 100.87.118.192 261 10.1.238.0 255.255.255.0 Auf Verbindung 100.87.118.192 6 10.1.238.255 255.255.255.255 Auf Verbindung 100.87.118.192 261 10.102.0.60 255.255.255.255 192.168.91.254 192.168.91.220 26 10.102.0.151 255.255.255.255 192.168.91.254 192.168.91.220 26 64.141.62.202 255.255.255.255 192.168.91.254 192.168.91.220 26 80.120.218.226 255.255.255.255 192.168.91.254 192.168.91.220 26 92.60.39.135 255.255.255.255 192.168.91.254 192.168.91.220 26 100.87.0.0 255.255.0.0 Auf Verbindung 100.87.118.192 261 100.87.118.192 255.255.255.255 Auf Verbindung 100.87.118.192 261 100.87.255.255 255.255.255.255 Auf Verbindung 100.87.118.192 261 127.0.0.0 255.0.0.0 Auf Verbindung 127.0.0.1 331 127.0.0.1 255.255.255.255 Auf Verbindung 127.0.0.1 331 127.255.255.255 255.255.255.255 Auf Verbindung 127.0.0.1 331 169.254.0.0 255.255.0.0 Auf Verbindung 169.254.34.24 291 169.254.0.0 255.255.0.0 Auf Verbindung 169.254.222.244 291 169.254.34.24 255.255.255.255 Auf Verbindung 169.254.34.24 291 169.254.222.244 255.255.255.255 Auf Verbindung 169.254.222.244 291 169.254.255.255 255.255.255.255 Auf Verbindung 169.254.34.24 291 169.254.255.255 255.255.255.255 Auf Verbindung 169.254.222.244 291 172.20.144.0 255.255.240.0 Auf Verbindung 172.20.144.1 5256 172.20.144.1 255.255.255.255 Auf Verbindung 172.20.144.1 5256 172.20.159.255 255.255.255.255 Auf Verbindung 172.20.144.1 5256 172.23.80.1 255.255.255.255 192.168.91.254 192.168.91.220 26 178.183.187.197 255.255.255.255 192.168.91.254 192.168.91.220 26 192.168.0.0 255.255.255.0 192.168.0.160 192.168.0.167 26 192.168.0.40 255.255.255.255 192.168.91.254 192.168.91.220 26 192.168.0.167 255.255.255.255 Auf Verbindung 192.168.0.167 281 192.168.0.243 255.255.255.255 192.168.91.254 192.168.91.220 26 192.168.91.0 255.255.255.0 Auf Verbindung 192.168.91.220 281 192.168.91.220 255.255.255.255 Auf Verbindung 192.168.91.220 281 192.168.91.255 255.255.255.255 Auf Verbindung 192.168.91.220 281 224.0.0.0 240.0.0.0 Auf Verbindung 127.0.0.1 331 224.0.0.0 240.0.0.0 Auf Verbindung 169.254.34.24 291 224.0.0.0 240.0.0.0 Auf Verbindung 169.254.222.244 291 224.0.0.0 240.0.0.0 Auf Verbindung 192.168.91.220 281 224.0.0.0 240.0.0.0 Auf Verbindung 172.20.144.1 5256 224.0.0.0 240.0.0.0 Auf Verbindung 192.168.0.167 281 224.0.0.0 240.0.0.0 Auf Verbindung 100.87.118.192 261 255.255.255.255 255.255.255.255 Auf Verbindung 127.0.0.1 331 255.255.255.255 255.255.255.255 Auf Verbindung 169.254.34.24 291 255.255.255.255 255.255.255.255 Auf Verbindung 169.254.222.244 291 255.255.255.255 255.255.255.255 Auf Verbindung 192.168.91.220 281 255.255.255.255 255.255.255.255 Auf Verbindung 172.20.144.1 5256 255.255.255.255 255.255.255.255 Auf Verbindung 192.168.0.167 281 255.255.255.255 255.255.255.255 Auf Verbindung 100.87.118.192 261 =========================================================================== Ständige Routen: Netzwerkadresse Netzmaske Gatewayadresse Metrik 0.0.0.0 0.0.0.0 192.168.91.254 Standard 0.0.0.0 0.0.0.0 192.168.91.254 256 =========================================================================== ``` </details> <details> <summary>Windows ipconfig</summary> ``` ipconfig /all Windows-IP-Konfiguration Hostname . . . . . . . . . . . . : uray-mic-dh Primäres DNS-Suffix . . . . . . . : Knotentyp . . . . . . . . . . . . : Hybrid IP-Routing aktiviert . . . . . . : Nein WINS-Proxy aktiviert . . . . . . : Nein DNS-Suffixsuchliste . . . . . . . : netbird.selfhosted lan.kw.uray.io mainserver.local Unbekannter Adapter wt0: Verbindungsspezifisches DNS-Suffix: netbird.selfhosted Beschreibung. . . . . . . . . . . : WireGuard Tunnel Physische Adresse . . . . . . . . : DHCP aktiviert. . . . . . . . . . : Nein Autokonfiguration aktiviert . . . : Ja IPv4-Adresse . . . . . . . . . . : 100.87.118.192(Bevorzugt) Subnetzmaske . . . . . . . . . . : 255.255.0.0 Standardgateway . . . . . . . . . : DNS-Server . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS über TCP/IP . . . . . . . : Aktiviert Suchliste für verbindungsspezifische DNS-Suffixe: netbird.selfhosted Ethernet-Adapter vEthernet (Switch LAN): Verbindungsspezifisches DNS-Suffix: lan.kw.uray.io Beschreibung. . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2 Physische Adresse . . . . . . . . : 2C-F0-5D-36-A4-2F DHCP aktiviert. . . . . . . . . . : Nein Autokonfiguration aktiviert . . . : Ja IPv4-Adresse . . . . . . . . . . : 192.168.91.220(Bevorzugt) Subnetzmaske . . . . . . . . . . : 255.255.255.0 Standardgateway . . . . . . . . . : 192.168.91.254 DNS-Server . . . . . . . . . . . : 192.168.91.254 NetBIOS über TCP/IP . . . . . . . : Aktiviert PPP-Adapter CTB VPN (IPsec): Verbindungsspezifisches DNS-Suffix: mainserver.local Beschreibung. . . . . . . . . . . : CTB VPN (IPsec) Physische Adresse . . . . . . . . : DHCP aktiviert. . . . . . . . . . : Nein Autokonfiguration aktiviert . . . : Ja IPv4-Adresse . . . . . . . . . . : 192.168.0.167(Bevorzugt) Subnetzmaske . . . . . . . . . . : 255.255.255.255 Standardgateway . . . . . . . . . : DNS-Server . . . . . . . . . . . : 192.168.0.32 192.168.0.31 NetBIOS über TCP/IP . . . . . . . : Aktiviert Ethernet-Adapter VMware Network Adapter VMnet1: Verbindungsspezifisches DNS-Suffix: Beschreibung. . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1 Physische Adresse . . . . . . . . : 00-50-56-C0-00-01 DHCP aktiviert. . . . . . . . . . : Nein Autokonfiguration aktiviert . . . : Ja Verbindungslokale IPv6-Adresse . : fe80::57e4:527c:b712:897f%22(Bevorzugt) IPv4-Adresse (Auto. Konfiguration): 169.254.34.24(Bevorzugt) Subnetzmaske . . . . . . . . . . : 255.255.0.0 Standardgateway . . . . . . . . . : DHCPv6-IAID . . . . . . . . . . . : 335564886 DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-26-9B-5C-E4-2C-F0-5D-36-A4-2F DNS-Server . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS über TCP/IP . . . . . . . : Aktiviert Ethernet-Adapter VMware Network Adapter VMnet8: Verbindungsspezifisches DNS-Suffix: Beschreibung. . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8 Physische Adresse . . . . . . . . : 00-50-56-C0-00-08 DHCP aktiviert. . . . . . . . . . : Nein Autokonfiguration aktiviert . . . : Ja Verbindungslokale IPv6-Adresse . : fe80::a920:b9c5:6ae7:1444%4(Bevorzugt) IPv4-Adresse (Auto. Konfiguration): 169.254.222.244(Bevorzugt) Subnetzmaske . . . . . . . . . . : 255.255.0.0 Standardgateway . . . . . . . . . : DHCPv6-IAID . . . . . . . . . . . : 503337046 DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-26-9B-5C-E4-2C-F0-5D-36-A4-2F DNS-Server . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS über TCP/IP . . . . . . . : Aktiviert Ethernet-Adapter vEthernet (Default Switch): Verbindungsspezifisches DNS-Suffix: Beschreibung. . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter Physische Adresse . . . . . . . . : 00-15-5D-28-33-A6 DHCP aktiviert. . . . . . . . . . : Nein Autokonfiguration aktiviert . . . : Ja Verbindungslokale IPv6-Adresse . : fe80::ad0:9a8d:e6c5:e867%46(Bevorzugt) IPv4-Adresse . . . . . . . . . . : 172.20.144.1(Bevorzugt) Subnetzmaske . . . . . . . . . . : 255.255.240.0 Standardgateway . . . . . . . . . : DHCPv6-IAID . . . . . . . . . . . : 771757405 DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-26-9B-5C-E4-2C-F0-5D-36-A4-2F DNS-Server . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS über TCP/IP . . . . . . . : Aktiviert ``` </details>
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 bug client routes
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#566
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?