mirror of
https://github.com/GNS3/gns3-server.git
synced 2026-10-12 13:35:31 +03:00
74010b9abd
The dynamips doc gets the full suite: anatomy (anchors reached by the hypervisors' TAP fds, uBridge's AF_PACKET-tap / tc-qdisc sidebands), a one-way copy-numbered relay comparison (six kernel/user crossings per way against the kernel datapath's two TAP-fd legs), a staged walkthrough (reserved-range diamond, egress clsact chain, capture/markers observation sideband, copies 1-2) and a control sequence of real commands in real order (hypervisor fd first, capture before markers, carrier last; router handlers, not computes, as the per-node participants). The four sibling frame paths are unified on the same form: netem qdisc node labels, one capture/markers node outside the stages with AF_PACKET tap edges anchored at ingress and post-chain egress, copy numbering wherever the trace crosses the kernel/user boundary (qemu's two TAP-fd legs, iol-docker's six socket/TAP legs), stage subgraphs with role-noted titles everywhere (iol-docker restructured from its flat chain, iou's chA/tapA variants folded into the canonical shapes). The documentation skill records the rules as v3.1.0: four diagram kinds (anatomy / comparison / control sequence / walkthrough), one step per node, dashed sidebands per role with meaningful direction, numbered crossings when copies are the point, glossary before the first diagram.