You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
net-test: packetdrill: make loose segmentation sequence errors more usable
With loose segementation (on by default), and a script line like:
+0 > . 3001:6001(3000) ack 1
...you could get a mystifying error message referring to a mysterious expected
sequence number of 12001 that the script did not really expect, without any
dumping of the expected or actual skbs to explain why:
bbr-fr-startup-sacks-grow-inflight.pkt:45: error handling packet:
live packet field tcp_seq: expected: 12001 (0x2ee1) vs actual: 3001 (0xbb9)
Now with this commit the error message dumps the full sequence of sniffed skbs,
along with the expected skb:
bbr-fr-startup-sacks-grow-inflight.pkt:45: error handling packet:
live packet field tcp_seq: expected: 12001 (0x2ee1) vs actual: 3001 (0xbb9)
script packet: 0.042528 . 3001:6001(3000) ack 1
actual #0 packet: 0.042468 . 10001:12001(2000) ack 1 win 256
actual #1 packet: 0.043177 . 3001:4001(1000) ack 1 win 256
With this info, the reader can see why a sequence of 12001 was expected by
packetdrill.
Signed-off-by: Neal Cardwell <[email protected]>
Change-Id: I932ce693a674efd320588fb6ab8b0aa67a961111
0 commit comments