Chapter 2: Ladder Arrows (-> / <-) & Lag (wait)

Keep client <-> server columns lined up like an ASCII sequence diagram and dial in exact microsecond or millisecond lag.

Labs completed0/7
The Situation · 5 min

It is always DNS. Fake a sluggish 250ms WAN resolver lookup so everyone can see what laggy DNS actually looks like in Wireshark time-delta columns.

What You'll Pull Off Here

  • Use <- so client and server stay pinned in their own visual columns while MACs, IPs, and ports swap automatically.
  • Dial in inter-packet gaps at the tail of any line with wait (ns, us, ms, s, m).
  • Craft real UDP DNS query -> response exchanges with matching txid values.
Interactive Lab Check

Lab 2: Inject 250ms WAN Lag & an Aligned <- Reply

Change wait 4ms to wait 250ms on the dns query line so Packet #2 lands at 250.000 ms, then append branch_pc <- erp_srv icmp echoreply id 200 seq 1 at the bottom of compile.

  1. 1.On line 7 (dns query), change wait 4ms to wait 250ms.
  2. 2.At the bottom of compile, add branch_pc <- erp_srv icmp echoreply id 200 seq 1.
  3. 3.Hit Check Exercise and eyeball the Time (ms) and Source -> Destination columns.

1. Stop Criss-Crossing Host Names: Use <-

In Lab 1 we flipped gateway -> laptop for the reply. Do that across a 20-packet exchange and your eyes will cross trying to figure out who is client and who is server.

That is why <- exists: writing branch_pc <- dns_wan dns response ... keeps branch_pc on the left and dns_wan on the right while firing the frame from dns_wan back to branch_pc (swapping MACs, IPs, and UDP/TCP ports automatically).

2. Post-Packet Time Travel with wait

Frame #1 always lands at 0.000 ms. Leave wait off a line and the compiler advances the clock by a polite 10ms before the next packet.

Slap wait 250ms (or 500us, 2s, 0ns) onto the end of Frame #1 and Frame #2 arrives exactly 250.000 ms later.

  • Units glue straight onto the number in lowercase: 0ns, 250us, 250ms, 2s, 1m.
  • wait is always an inline suffix on a packet line — never put wait 250ms alone on its own line.
  • Strings like qname "erp.corp.local" always wear double quotes "...", never single quotes.
Word-by-Word Syntax Breakdown
Column-aligned <- reply + post-packet wait timer:
branch_pc <- dns_wan dns response txid 0x2a10 qname "erp.corp.local" qtype "A" rdata "10.80.1.20" wait 5ms
branch_pc <- dns_wanReply ArrowSends from dns_wan (53) back to branch_pc (49152) without flipping columns
dns responseProtocolDNS standard query response over UDP port 53
txid 0x2a10Transaction IDMatches the 16-bit ID from the query above it
rdata "10.80.1.20"Answer RecordPacks the IPv4 A-record into the DNS answer section
wait 5msPost-Packet GapAdvances the capture clock by 5 ms before the next line
Quick Formatting Reference (2 rules)
ItemValid .frasmAvoid
Where wait livesbranch_pc -> dns_wan dns query qname "erp.corp.local" wait 250mswait 250ms // standalone wait line is a syntax error
Quotesqname "erp.corp.local" qtype "A"qname 'erp.corp.local' qtype 'A'
wan_dns_latency.frasmLoading WASM…
Wireshark filter: dns || icmp
Open in Playground
0 B · 0.000 ms
Compiling capture in WebAssembly…
Learn .frasm — Labs, Guides & 81 Protocols | FrameAssembly