mirror of
https://github.com/GNS3/gns3-server.git
synced 2026-08-29 05:20:14 +03:00
239f42f5aa
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.