mirror of
https://github.com/GNS3/gns3-server.git
synced 2026-11-19 04:35:14 +02:00
docs: dynamips kernel-datapath diagram suite, unified frame-path form across the family
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.
This commit is contained in:
6 files changed
+264
-145
No files matched your search
@@ -155,8 +155,9 @@ flowchart LR
|
||||
subgraph GVB["gvB — egress chain (clsact, then netem)"]
|
||||
S5["eBPF prio 1"]
|
||||
S6["bpf_drop prio 10-99"]
|
||||
S7["netem"]
|
||||
S7["netem qdisc"]
|
||||
end
|
||||
T["capture / markers"]
|
||||
end
|
||||
subgraph BNS["container B netns"]
|
||||
S9["eth0 B receives"]
|
||||
@@ -168,9 +169,11 @@ flowchart LR
|
||||
S4 --> S5
|
||||
S5 --> S6 --> S7
|
||||
S7 -->|"veth pair"| S9
|
||||
S3 -. "AF_PACKET tap" .-> T
|
||||
S7 -. "AF_PACKET tap" .-> T
|
||||
```
|
||||
|
||||
What each stage drops: the reserved-range gate passes LACP, LLDP, 802.1X and STP per the port mask but never PAUSE/PFC (Link-local frames below); the clsact/netem stages drop or impair per the installed filters (Packet filters below). The AF_PACKET taps observe both host ends but never a clsact-dropped frame.
|
||||
What each stage drops: the reserved-range gate passes LACP, LLDP, 802.1X and STP per the port mask but never PAUSE/PFC (Link-local frames below); the clsact/netem stages drop or impair per the installed filters (Packet filters below). Whichever end hosts capture / markers, its AF_PACKET tap — the dashed sideband above — clones the frame at that anchor: a tap on gvA sees the frame on arrival, a tap on gvB only if the clsact chain let it through.
|
||||
|
||||
All dozen-plus GNS3 filter types ride these three kernel objects — nine of them (delay, packet_loss, corrupt, duplicate, rate, reorder, gemodel, seed, limit) are parameters of the single netem qdisc, `bpf` expressions are the cls_bpf filters, and frequency_drop / quota / window_drop are the three modes inside the one eBPF program (evaluated nth → quota → window). The complete type-to-object mapping is the Packet filters table below.
|
||||
|
||||
|
||||
Reference in new issue
Block a user