Cannot access internal LAN when netbird is up

Community Support Linux
1

Describe the problem

I have a proxmox vm that is connected to netbird. This client also used an exit node. ( server has some docker containers inside for example on port 3000, lingva). When netbird is up, i cannot reach these docker containets. As soon as netbird is down, i can access the dockers again.

To Reproduce

Create a client in linux.
Netbird up with exit node
Try to reach the server using local ip (10.0.20.100)

Expected behavior

Local.ip should work when server is in my local LAN even though netbird is.up.

Are you using NetBird Cloud?

Netbird cloud

NetBird version

0.54.0

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

1000009258
10000092581008Ă—2244 279 KB

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

netbird debug for 1m -AS -U

Uploaded files are automatically deleted after 30 days.

Alternatively, create the file only and attach it here manually:

netbird debug for 1m -AS

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

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
2

Are you trying to reach the docker containers over Netbird or through their own internal IP address from docker itself?

3

I am trying to reach them from their internal IP address (10.0.20.102), but with one caveat, I am on another subnet/VLAN (10.0.10.x). I cannot reach them through this subnet (10.0.10.x), but I can only reach the netbird VM within their own subnet, where the netbird VM also is (10.0.20.x)

4

Ouch, that’s a bit more unique. Subnets are interesting to say the least. It could be your routing is a bit scuffed, but you’d have to check with the networking on that part. Woudn’t be able to say.

5

hmm. thanks for trying to help. Any direction to take, or any tips for further research is appreciated.