routing-troubleshooting

Diagnose NetBird routing issues on Linux using ip and systemctl.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/renne/skills --skill routing-troubleshooting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: routing-troubleshooting
Source: https://github.com/renne/skills/tree/main/netbird/routing-troubleshooting
Command: npx skills add https://github.com/renne/skills --skill routing-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose and resolve complex routing problems on Linux systems using NetBird, particularly when traffic fails to reach remote subnets or experiences asymmetric routing.

Core Features & Use Cases

  • Diagnose Asymmetric Routing: Identify and fix issues where traffic flows in one direction but fails in the other due to NetBird's policy routing.
  • Resolve Stale Routes: Troubleshoot and remove outdated routes left behind by removed NetBird peers.
  • Override NetBird Routes: Implement static route overrides to ensure correct traffic flow through specific interfaces.
  • Use Case: A server on a remote subnet can ping your NetBird peer, but TCP connections fail. This Skill guides you through checking NetBird's routing table and applying a fix.

Quick Start

Use the routing-troubleshooting skill to diagnose why a host is reachable via LAN but not from a remote subnet routed through a gateway.

Frequently Asked Questions about routing-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does ping succeed but TCP connections fail when routing to a remote subnet through NetBird?

Asymmetric routing on Linux often causes ping to succeed while TCP fails. NetBird's policy routing table 7120 can route return traffic incorrectly, dropping TCP state. Diagnose the flow using the `ip` command to inspect routing rules and apply static route overrides to fix it.

How do I troubleshoot a Linux host reachable via LAN but not from a remote NetBird subnet?

Troubleshoot NetBird routing by checking policy routing table 7120 for unexpected subnets or stale routes from removed peers. Use the `ip` command to verify route paths and `systemctl` to restart the NetBird service, clearing outdated network state.

How do I remove stale routes left by removed NetBird peers on Linux?

Remove stale NetBird routes by inspecting policy routing table 7120 with the `ip` command to identify outdated subnets. Flush the incorrect routes and restart the NetBird service via `systemctl` to ensure the routing table only contains active peer networks.

What is NetBird policy routing table 7120 and when do I need to inspect it?

NetBird policy routing table 7120 is a Linux routing table managing traffic for remote subnets. Inspect it when you experience asymmetric routing or unexpected subnet behavior, using the `ip` command to verify if static route overrides are needed to correct traffic flow.

Can I override NetBird routes with static routes on Linux to fix asymmetric routing?

Yes, you can implement static route overrides on Linux to correct asymmetric routing caused by NetBird. By configuring static routes, you ensure traffic flows through specific interfaces correctly, bypassing conflicting policy routing table 7120 entries.

Does routing-troubleshooting require specific Linux commands to diagnose NetBird issues?

Yes, diagnosing NetBird routing issues requires the `ip` command for checking policy routing tables and interface paths, and `systemctl` for restarting the NetBird service to apply route changes or clear stale peer entries.