From 9bed54d3be93774211dc7f4b1ff43c0b2ecb8269 Mon Sep 17 00:00:00 2001 From: jochens Date: Fri, 2 Oct 2026 12:22:15 +0200 Subject: [PATCH] Issue 197 resolved: the wired port is guarded before it is plugged in --- .../00-report.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/04-ISSUES/197-a-physical-link-that-is-down-is-not-filtered-when-it-comes-up/00-report.md b/04-ISSUES/197-a-physical-link-that-is-down-is-not-filtered-when-it-comes-up/00-report.md index 1199623..c076999 100644 --- a/04-ISSUES/197-a-physical-link-that-is-down-is-not-filtered-when-it-comes-up/00-report.md +++ b/04-ISSUES/197-a-physical-link-that-is-down-is-not-filtered-when-it-comes-up/00-report.md @@ -1,8 +1,8 @@ --- -status: located +status: resolved opened: 2026-10-02 located-in: [mesh-host internal/outward (Links reported only the links carrying a default route)] -fixed-by: +fixed-by: mesh-host PR 66 (a link backed by a physical device is named outward, up or down), live 2026-10-02 amended-design: [] --- @@ -36,3 +36,8 @@ that never carries the default route, such as a direct link to a storage box, is - A virtual link that faces outside (a VPN client's interface, a USB tether that appears as a virtual device) has no physical device behind it. It is named only while it carries the default route. Is that enough? + +## Resolved (2026-10-02) + +Live on the affected machine after the host was delivered and one more push: its filter now guards the +radio, the tunnel and the unplugged wired port, before anything is plugged into it.