[GH-ISSUE #5812] macOS: Network route not installed in OS routing table despite Status: Selected #11790

Open
opened 2026-08-05 01:31:01 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @Optic00 on GitHub (Apr 7, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5812

Describe the problem:
On macOS, a configured Network (192.168.178.0/24) shows as Status: Selected in netbird networks ls, and the log shows the route being added as WireGuard AllowedIP on utun100 — but the route is never written to the macOS routing table. Traffic continues to flow via the default gateway.

Manually adding the route fixes the issue immediately:

sudo route add -net 192.168.178.0/24 -interface utun100

To Reproduce:

  • Configure a Network in Netbird dashboard with a remote LAN (e.g. 192.168.178.0/24)
  • Set a Debian Linux peer as routing peer
  • Connect macOS client
  • Run netbird networks ls → Status shows Selected
  • Run netstat -rn | grep 192.168.178 → no entry
  • Run traceroute 192.168.178.1 → goes via default gateway, not via utun

Expected behavior:
The route should be installed in the macOS routing table automatically when the Network Status is Selected.

Workaround:
Manually setting the route works:

sudo route add -net 192.168.178.0/24 -interface utun100

Logs:
Adding allowed IP to interface utun100 and peer ...: allowed IP 192.168.178.0/24
AllowedIP is set correctly on the WireGuard interface, but no corresponding OS route is written to the macOS routing table.

Environment:

OS: macOS Tahoe 26.3, Apple Silicon (Mac Mini M4)
Daemon version: 0.67.4
CLI version: 0.67.4
Interface type: Kernel
Routing peer OS: Debian Linux
Routing peer Netbird version: 0.67.4

Originally created by @Optic00 on GitHub (Apr 7, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5812 **Describe the problem:** On macOS, a configured Network (192.168.178.0/24) shows as Status: Selected in netbird networks ls, and the log shows the route being added as WireGuard AllowedIP on utun100 — but the route is never written to the macOS routing table. Traffic continues to flow via the default gateway. Manually adding the route fixes the issue immediately: `sudo route add -net 192.168.178.0/24 -interface utun100 ` **To Reproduce:** - Configure a Network in Netbird dashboard with a remote LAN (e.g. 192.168.178.0/24) - Set a Debian Linux peer as routing peer - Connect macOS client - Run netbird networks ls → Status shows Selected - Run netstat -rn | grep 192.168.178 → no entry - Run traceroute 192.168.178.1 → goes via default gateway, not via utun **Expected behavior:** The route should be installed in the macOS routing table automatically when the Network Status is Selected. **Workaround:** Manually setting the route works: `sudo route add -net 192.168.178.0/24 -interface utun100 ` **Logs:** Adding allowed IP to interface utun100 and peer ...: allowed IP 192.168.178.0/24 AllowedIP is set correctly on the WireGuard interface, but no corresponding OS route is written to the macOS routing table. **Environment:** OS: macOS Tahoe 26.3, Apple Silicon (Mac Mini M4) Daemon version: 0.67.4 CLI version: 0.67.4 Interface type: Kernel Routing peer OS: Debian Linux Routing peer Netbird version: 0.67.4
saavagebueno added the triage-needed label 2026-08-05 01:31:01 -04:00
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#11790