Issue 197 resolved: the wired port is guarded before it is plugged in

This commit is contained in:
2026-10-02 12:22:15 +02:00
parent 413daf8ad5
commit 9bed54d3be
@@ -1,8 +1,8 @@
--- ---
status: located status: resolved
opened: 2026-10-02 opened: 2026-10-02
located-in: [mesh-host internal/outward (Links reported only the links carrying a default route)] 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: [] 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 - 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 device) has no physical device behind it. It is named only while it carries the default route. Is
that enough? 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.