connectivity-troubleshooting

Configure TCP keepalive and systemd overrides to resolve Netbird WireGuard ENOKEY errors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves persistent Netbird connectivity failures on Linux systems, particularly those behind restrictive NAT devices like FritzBox routers, which often lead to WireGuard ENOKEY errors and require reboots to restore service.

Core Features & Use Cases

  • Diagnose NAT Issues: Identifies how router TCP NAT timeouts break Netbird's relay connections.
  • Automate Fixes: Implements system-level TCP keepalive tuning and systemd service overrides to ensure stable Netbird operation.
  • Use Case: When your Netbird VPN peers become unreachable after a period of uptime, and netbird down && netbird up is the only temporary fix, this skill provides the permanent solution.

Quick Start

Apply the recommended TCP keepalive tuning to resolve Netbird connectivity issues.

Frequently Asked Questions about connectivity-troubleshooting

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

FAQPage Schema
Why does Netbird keep losing connectivity and throwing WireGuard ENOKEY errors on Linux?

Netbird connectivity failures with WireGuard ENOKEY errors on Linux are typically caused by router TCP NAT timeouts breaking relay connections, requiring reboots or manual restarts to restore service.

How do I permanently fix Netbird VPN peers becoming unreachable behind a NAT router?

To permanently fix Netbird VPN peers becoming unreachable behind NAT, apply system-level TCP keepalive tuning and systemd service overrides to maintain stable relay connections without manual intervention.

What is the best way to configure TCP keepalive on Linux for WireGuard VPN stability?

The best way to configure TCP keepalive for WireGuard VPN stability on Linux involves modifying sysctl parameters to adjust keepalive intervals and creating systemd unit overrides for persistent application.

Does this Netbird troubleshooting approach work for Linux peers behind FritzBox routers?

Yes, this Netbird troubleshooting approach specifically targets Linux peers behind restrictive NAT devices like FritzBox routers, resolving the TCP timeout issues that cause persistent connectivity drops.

When should I use systemd overrides instead of running netbird down and up repeatedly?

Use systemd overrides when `netbird down && netbird up` only provides a temporary fix, as implementing service overrides with TCP keepalive tuning ensures persistent network stability without manual reboots.