[GH-ISSUE #1807] From network B to network A everything is ok, but from A to B only ping and traceroute work #3454

Open
opened 2026-08-05 00:52:29 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @Nexulo on GitHub (Apr 5, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1807

I have a very specific problem:

Network A (external network: 192.168.10.0/24) and network B (my home network: 192.168.184.0/24) are connected via two peers (2x Raspberry Pi 4) via Netbird. I can access all clients on external network A from my home network B. The peer in network A routes all requests correctly to the clients in the network and I can access the WebUI of various clients in this network.

If I am now connected over Wifi to network A and want to access devices located in home network B, only ping and traceroute commands works. The routing etc. all seems to work, because I can ping the devices and traceroute to the devices also works. But I still can't establish an SSH connection to clients in network B, no matter which target device I have. I also cannot access the WebUI from any client in network B. But as i said, ping and traceroute are always working.

Maybe my problem is related to this:
https://github.com/netbirdio/netbird/issues/743

Peers:

Network A - 192.168.10.111
Network B - 192.168.184.43

Traceroute from Network B to Network A:

❯ traceroute 192.168.10.111
traceroute to 192.168.10.111 (192.168.10.111), 64 hops max, 40 byte packets
 1  192.168.184.1 (192.168.184.1)  3.522 ms  2.179 ms  2.177 ms
 2  192.168.184.43 (192.168.184.43)  2.513 ms  3.283 ms  2.551 ms
 3  192.168.10.111 (192.168.10.111)  81.484 ms  68.183 ms  63.558 ms

Traceroute from Network A to Network B:

❯ traceroute 192.168.184.43
traceroute to 192.168.184.43 (192.168.184.43), 64 hops max, 40 byte packets
 1  router.asus.com (192.168.10.1)  4.142 ms  2.159 ms  1.905 ms
 2  raspberry-extern (192.168.10.111)  1.924 ms  2.262 ms  1.659 ms
 3  192.168.184.43 (192.168.184.43)  59.853 ms  75.364 ms  64.368 ms

Pings with zero paket loss

❯ ping -c 100 192.168.184.24
PING 192.168.184.24 (192.168.184.24): 56 data bytes
64 bytes from 192.168.184.24: icmp_seq=0 ttl=62 time=63.984 ms
...
64 bytes from 192.168.184.24: icmp_seq=95 ttl=62 time=84.316 ms
64 bytes from 192.168.184.24: icmp_seq=96 ttl=62 time=62.566 ms
64 bytes from 192.168.184.24: icmp_seq=97 ttl=62 time=78.672 ms
64 bytes from 192.168.184.24: icmp_seq=98 ttl=62 time=111.832 ms
64 bytes from 192.168.184.24: icmp_seq=99 ttl=62 time=87.197 ms

--- 192.168.184.24 ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss

The strange thing:
I can successfully run a curl command in the cli of my peer in network A to a Client in Network B, but when i run the same command on my Mac Book, which is connected to Network A too, i get this (it's stuck and never finishes):

❯ curl -kv 192.168.184.24
*   Trying 192.168.184.24:80...
* Connected to 192.168.184.24 (192.168.184.24) port 80
> GET / HTTP/1.1
> Host: 192.168.184.24
> User-Agent: curl/8.4.0
> Accept: */*
> 

Are you using NetBird Cloud?
No i'm using a self-hosted Netbird server.

NetBird version
I've installed everything today, so i have the newest version.

NetBird status -d output:

Peers detail:
 raspberry-intern.netbird.selfhosted:
  NetBird IP: 100.92.55.27
  Public key: <>
  Status: Connected
  -- detail --
  Connection type: Relayed
  Direct: true
  ICE candidate (Local/Remote): host/relay
  ICE candidate endpoints (Local/Remote): 192.168.10.111:51820/<>:51820
  Last connection update: 2024-04-05 14:37:12
  Last WireGuard handshake: 2024-04-05 19:28:50
  Transfer status (received/sent) 77.9 KiB/105.7 KiB
  Quantum resistance: false
  Routes: 192.168.184.0/24
  Latency: 74.996393ms

Daemon version: 0.27.1
CLI version: 0.27.1
Management: Connected to https://domain.com:443
Signal: Connected to https://domain.com:443
Relays: 
  [stun:domain.com:3478] is Available
  [turn:domain.com:3478?transport=udp] is Available
Nameservers: 
FQDN: raspberry-extern.netbird.selfhosted
NetBird IP: 100.92.160.180/16
Interface type: Kernel
Quantum resistance: false
Routes: -
Peers count: 1/1 Connected
Originally created by @Nexulo on GitHub (Apr 5, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1807 I have a very specific problem: Network A (external network: 192.168.10.0/24) and network B (my home network: 192.168.184.0/24) are connected via two peers (2x Raspberry Pi 4) via Netbird. I can access all clients on external network A from my home network B. The peer in network A routes all requests correctly to the clients in the network and I can access the WebUI of various clients in this network. If I am now connected over Wifi to network A and want to access devices located in home network B, only ping and traceroute commands works. The routing etc. all seems to work, because I can ping the devices and traceroute to the devices also works. But I still can't establish an SSH connection to clients in network B, no matter which target device I have. I also cannot access the WebUI from any client in network B. But as i said, ping and traceroute are always working. Maybe my problem is related to this: https://github.com/netbirdio/netbird/issues/743 **Peers:** ``` Network A - 192.168.10.111 Network B - 192.168.184.43 ``` **Traceroute from Network B to Network A:** ``` ❯ traceroute 192.168.10.111 traceroute to 192.168.10.111 (192.168.10.111), 64 hops max, 40 byte packets 1 192.168.184.1 (192.168.184.1) 3.522 ms 2.179 ms 2.177 ms 2 192.168.184.43 (192.168.184.43) 2.513 ms 3.283 ms 2.551 ms 3 192.168.10.111 (192.168.10.111) 81.484 ms 68.183 ms 63.558 ms ``` **Traceroute from Network A to Network B:** ``` ❯ traceroute 192.168.184.43 traceroute to 192.168.184.43 (192.168.184.43), 64 hops max, 40 byte packets 1 router.asus.com (192.168.10.1) 4.142 ms 2.159 ms 1.905 ms 2 raspberry-extern (192.168.10.111) 1.924 ms 2.262 ms 1.659 ms 3 192.168.184.43 (192.168.184.43) 59.853 ms 75.364 ms 64.368 ms ``` **Pings with zero paket loss** ``` ❯ ping -c 100 192.168.184.24 PING 192.168.184.24 (192.168.184.24): 56 data bytes 64 bytes from 192.168.184.24: icmp_seq=0 ttl=62 time=63.984 ms ... 64 bytes from 192.168.184.24: icmp_seq=95 ttl=62 time=84.316 ms 64 bytes from 192.168.184.24: icmp_seq=96 ttl=62 time=62.566 ms 64 bytes from 192.168.184.24: icmp_seq=97 ttl=62 time=78.672 ms 64 bytes from 192.168.184.24: icmp_seq=98 ttl=62 time=111.832 ms 64 bytes from 192.168.184.24: icmp_seq=99 ttl=62 time=87.197 ms --- 192.168.184.24 ping statistics --- 100 packets transmitted, 100 packets received, 0.0% packet loss ``` **The strange thing:** I can successfully run a curl command in the cli of my peer in network A to a Client in Network B, but when i run the same command on my Mac Book, which is connected to Network A too, i get this (it's stuck and never finishes): ``` ❯ curl -kv 192.168.184.24 * Trying 192.168.184.24:80... * Connected to 192.168.184.24 (192.168.184.24) port 80 > GET / HTTP/1.1 > Host: 192.168.184.24 > User-Agent: curl/8.4.0 > Accept: */* > ``` **Are you using NetBird Cloud?** No i'm using a self-hosted Netbird server. **NetBird version** I've installed everything today, so i have the newest version. **NetBird status -d output:** ``` Peers detail: raspberry-intern.netbird.selfhosted: NetBird IP: 100.92.55.27 Public key: <> Status: Connected -- detail -- Connection type: Relayed Direct: true ICE candidate (Local/Remote): host/relay ICE candidate endpoints (Local/Remote): 192.168.10.111:51820/<>:51820 Last connection update: 2024-04-05 14:37:12 Last WireGuard handshake: 2024-04-05 19:28:50 Transfer status (received/sent) 77.9 KiB/105.7 KiB Quantum resistance: false Routes: 192.168.184.0/24 Latency: 74.996393ms Daemon version: 0.27.1 CLI version: 0.27.1 Management: Connected to https://domain.com:443 Signal: Connected to https://domain.com:443 Relays: [stun:domain.com:3478] is Available [turn:domain.com:3478?transport=udp] is Available Nameservers: FQDN: raspberry-extern.netbird.selfhosted NetBird IP: 100.92.160.180/16 Interface type: Kernel Quantum resistance: false Routes: - Peers count: 1/1 Connected ```
saavagebueno added the triage-needed label 2026-08-05 00:52:29 -04:00
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#3454