# Captured inside an isolated Linux networking lab; the original five-interface capture is included. sequence missing-packet-r1 "A missing TCP reply · R1 · missing arrival" { version 0.2 theme blueprint actor client "Client" description "192.0.2.10" actor gateway "Gateway" description "Inner TCP" actor r1 "R1" description "Client side" actor r2 "R2" description "Service side" actor service "Service" description "Port 443" actor ingress "R1 ingress" description "No matching SYN-ACK" actor egress "R2 egress" description "SYN-ACK captured" message clienthop client -> gateway "SYN" message gatewayhop gateway -> r1 "Forward SYN" message routerhop r1 -> r2 "SYN toward R2" message servicehop r2 -> service "SYN reaches service" reply answer service -> r2 "SYN-ACK" reply tapout r2 -> egress "Seen leaving R2" reply missingleg egress -> ingress "Expected · not seen at R1" kind unobserved cite "https://www.rfc-editor.org/rfc/rfc9293.html#section-3.5" "TCP connection establishment · RFC 9293 §3.5" target answer story investigate "R1 · missing arrival" { step inspect focus r1,ingress duration 550 step cross flow routerhop duration 700 step receive flow servicehop duration 700 step reply flow answer duration 950 step observe flow tapout duration 780 step compare focus missingleg,egress,ingress duration 550 step retry flow clienthop duration 820 } }