From e3ce234a09b92ea43bfbf055f98594a95d9d0b26 Mon Sep 17 00:00:00 2001 From: YueGuobin Date: Mon, 3 Aug 2026 00:05:08 +0800 Subject: [PATCH] docs: add log-interpretation note across node types for marker operations --- docs/features/marker-traffic-insight.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/features/marker-traffic-insight.md b/docs/features/marker-traffic-insight.md index 3ca90e891..1995b414d 100644 --- a/docs/features/marker-traffic-insight.md +++ b/docs/features/marker-traffic-insight.md @@ -341,3 +341,12 @@ direction relative to the capture node; see [Direction](#direction). - **Persistence.** Definitions and private markers persist in the topology; inherited markers are re-created from definitions on project load, so reopening a project restores the same configuration and stale inherited copies cannot survive on disk. +- **Log interpretation across node types.** Each node type logs its startup and link + operations differently — do not mistake sparse logs from one type for inactivity. + QEMU prints `set_link gns3- on` via its QEMU monitor, which is the most visible + startup log among all types. VPCS, Docker, IOU, Dynamips, and Cloud each have their own + startup paths (fork + ubridge, container veth, iouyap, Dynamips hypervisor, and TAP + device respectively) and none of them emit QEMU-monitor-style logs. To verify marker + operations (toggle, pause, resume) on non-QEMU types, either inspect uBridge's + own log for `enable_packet_filter` / `marker pause` / `marker resume` commands, or + watch the gns3server log for the corresponding compute-route calls at INFO level.