Network Route 192.168.10.0/24 not appearing in OS routing table (wt0) despite being configured in Dashboard

General Discussion
1

Hello
I have a site-to-site setup where I need to route traffic between two locations. Connection between peers is stable, but the routes are not being pushed to the OS routing table.

Topology:

  • Office: 192.168.100.0/24 (Routing Peer: Ubuntu 22.04)

  • Data Center (DC): 192.168.10.0/24 (Routing Peer: Ubuntu 22.04, also hosting the Management Server)

The Issue: On the Office Peer, ip route show does not show the route to the DC network (192.168.10.0/24 dev wt0).

My Configuration in Dashboard:

  1. Network Route: Created for 192.168.10.0/24 with the DC Peer as the routing node.

  2. Access Control: Policies are set to “Accept” between the Office group and the DC Peer/Network.

  3. IP Forwarding/Masquerade: Enabled on both routing peers.

Observations:

  • netbird status shows the management and signal servers are connected.

  • Manual addition of the route (ip route add 192.168.10.0/24 dev wt0) temporarily fixes the connectivity, which confirms the tunnel itself is working.

  • However, NetBird does not manage this route automatically.

Question: What could prevent the NetBird agent from adding the configured Network Route to the system’s routing table? Are there specific logs I should check to see why the agent is ignoring the route configuration from the Management server?

2

Did you re-up the peers? I often find that things don’t “stick” until I do that.