Bypass sets an ipv6 default route 'via None' on networks without ipv6 #160

New issue

Closed

opened 2026-08-24 18:34:23 -04:00 by mysticalsoap · 0 comments

mysticalsoap commented

2026-08-24 18:34:23 -04:00

Owner

Every bypass rebuild on a network with no ipv6 gateway logs

ERROR - Bypass: Failed to set ipv6 route 'default via None dev enp5s0'

create_cgroup interpolates the routes dict's gateway_6 straight into ip -6 route replace default via {gw_6} ... — and with no ipv6 connectivity that value is the literal string None, so the command can only fail. The v4 branch has the same shape but always has a real gateway in practice.

Skip the v6 route (log debug, not error) when gateway_6 is "None" — same convention observer.default_routes already uses for absent gateways. Fires on every service start, network change and settings apply, so it reads like something is broken when nothing is.

🤖 Generated with Claude Code

Every bypass rebuild on a network with no ipv6 gateway logs ``` ERROR - Bypass: Failed to set ipv6 route 'default via None dev enp5s0' ``` `create_cgroup` interpolates the routes dict's `gateway_6` straight into `ip -6 route replace default via {gw_6} ...` — and with no ipv6 connectivity that value is the literal string `None`, so the command can only fail. The v4 branch has the same shape but always has a real gateway in practice. Skip the v6 route (log debug, not error) when `gateway_6` is "None" — same convention `observer.default_routes` already uses for absent gateways. Fires on every service start, network change and settings apply, so it reads like something is broken when nothing is. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

mysticalsoap added the

bug

label

2026-08-24 18:34:23 -04:00

mysticalsoap referenced this issue from a pull request that will close it,

2026-08-24 19:56:07 -04:00

Quiet the log: expected states stop reporting as failures #163

mysticalsoap closed this issue

2026-08-24 20:16:15 -04:00