Make data-seq-number and data-ack relative

[aschils]

Make data-seq-number and data-ack relative

[cpaasch]

The bug should be reopened - it does not work when sending out-of-order data:

0   socket(..., SOCK_STREAM, IPPROTO_TCP) = 3
+0  setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
+0  bind(3, ..., ...) = 0
+0  listen(3, 1) = 0

+0  < S 0:0(0) win 32792 <mss 1460,nop,wscale 7,mp_capable a>
+0  > S. 0:0(0) ack 1 <mss 1460,nop,wscale 7, mp_capable b>
+0  < . 1:1(0) ack 1 win 257 <mp_capable a b, dss dack4> //=trunc_r64_hmac(b)>
+0  accept(3, ..., ...) = 4

+0  write(4, ..., 1000) = 1000
+0  > P. 1:1001(1000) ack 1 <dss dack4 dsn4 >
+0 < . 1:1(0) ack 1001 win 225 <dss dack4>

+0.1 < PF. 1001:1002(1) ack 1001 win 257 <dss dack4 dsn4=1001 ssn=1000 dll=2>
+0 > . 1001:1001(0) ack 1 <dss dack4=1>

The PF-packet is actually out-of-order. But this should not affect the expected data-ack.

What I get is the following:

./bug_39_01.pkt:16: error handling packet: bad outbound TCP options
script packet:  0.119875 . 1001:1001(0) ack 1 <dss dack4 16777216 flags: A>
actual packet:  0.119866 . 1001:1001(0) ack 1 win 225 <dss dack4 1175431638 flags: A>

It is expecting the incorrect data-ack.