YueGuobin 239f42f5aa
fix(marker): stop auto-deleting markers on node stop in node_updated
Markers are persistent link-scoped features (like packet filters), not
transient runtime features (like capture).  Tearing them down on every
node stop breaks stop/start restore: the NIO-based re-application in
_ubridge_apply_markers works correctly on restart, but node_updated
was prematurely calling stop_marker which erased _markers state and
dumped an empty topology.

Now markers survive node stop transparently — the ubridge filter dies
with the process but is re-added from nio.markers in
add_ubridge_udp_connection when the node starts again, mirroring
exactly how packet filters behave.
2026-07-16 00:39:51 +08:00
..
2026-06-16 23:04:05 +08:00
2026-04-11 19:22:05 +08:00
2026-05-09 18:23:00 +08:00
2026-06-16 00:34:11 +08:00
2026-05-09 18:23:00 +08:00
2024-04-22 19:08:45 +07:00
2026-03-11 18:51:32 +01:00