cannot access the internal IP of a routing peer

[lucasd23]

Describe the problem

I cannot access the internal IP of a routing peer if I am actively using that peer for routing.

To Reproduce

Steps to reproduce the behavior:

1. Set up routing peer with access to 192.168.30.0/24. Routing Peer has internal IP of 192.168.30.5
2. Ping NetBird IP of routing peer - succeeds
3. Ping internal IP (192.168.30.5) - Request timed out
   Expected behavior

Pinging 192.168.30.5 should succeed.

Are you using NetBird Cloud?

Using NetBird Self Hosted

NetBird version

51.2

Is any other VPN software installed?

No

Debug output

To help us resolve the problem, please attach the following anonymized status output

netbird status -dA

netbird status -dA.txt

Create and upload a debug bundle, and share the returned file key:

netbird debug for 1m -AS -U

799a6d96a7edf0e36805efc25c8b946c5e12366c37a058395649b205b0082ce9/35357d15-0033-406e-86a4-bdae2917fc84

Uploaded files are automatically deleted after 30 days.

Have you tried these troubleshooting steps?

• Reviewed client troubleshooting (if applicable)
• Checked for newer NetBird versions
• Searched for similar issues on GitHub (including closed ones)
• Restarted the NetBird client
• Disabled other VPN software
• Checked firewall settings

[lixmal]

Could you please create a debug bundle on the routing peer?
First thing that you can check is that you have a policy allowing access to the peer in addition to the policy allowing access to the resource.

[saule1508]

isn't it what @nazarewk explains here ? netbirdio/docs#401

[lucasd23]

isn't it what @nazarewk explains here ? netbirdio/docs#401

Yes, it looks like what I am seeing is expected behavior. I moved around which devices I was using as routing peers it it should be fine.