Random Ping Timeouts when using Agent on VM with public IP

Community Support Self-Hosted
1

Describe the problem

Random ping timeouts when agent is running on a VM with a public IP.

I’am pinging the VM via it’s public IP and it looks like my machine is sometimes trying to reach the VM over the public IP and sometimes over Netbird but I’am not sure. As soon as i stop the agent on the server, pings are normal.

Basically i just want to know: Is it bad to install a netbird agent on a VM with a public IP too?
My idea was to use the public IP for normal web traffic, and Netbird for exposing some internal management dashboards.
Can i somehow tell the agent to not publish the server’s public IP to the client so i can only use the IP assigend by Netbird?

To Reproduce

Steps to reproduce the behavior:

  1. Install Netbird Agent on a VM with a public IP
  2. Install Netbord Agent on client machine
  3. Create a Policy
  4. Try to ping the VM’s public IP

Expected behavior

Pings to a public IP should always be routes to the public IP directly.

Are you using NetBird Cloud?

No, self-hosted.

NetBird version

v0.58.2

Is any other VPN software installed?

No

Debug output

Here is a dump from the VM:
1f70b97ffde3a8a0183e3b7b8be8c9544392b2a7709e9bc9526e468232e012f6/2a9fec3c-1188-43c8-bc49-3bedd615e7c5

And here from my local machine:
1f70b97ffde3a8a0183e3b7b8be8c9544392b2a7709e9bc9526e468232e012f6/9d17d7f9-9349-4fef-81f1-1bb6d21ece34

Screenshots

image
image1920×1250 107 KB

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

Public traffic shoudn’t be affected unless you assign the VM a route that makes it follow a different connection with like an exit node. Check your policies, or reset the configuration for that machine in the NB panel and see if that affects the ping in anyway.