SACK (and PF) wierdness

[Pawel Worach]

Hi Max,

Max Laier wrote:
> 
> These two make no sense at all (at least to me). seq + len is over the window 
> by 1136 and I don't have the slightest clue why that would be the case. I am 
> also a bit surprised that the two (three) state failures are so close 
> together (04:27:35 and 04:27:40). Really strange.
I just did a new test, a little bit more synchronized this time.

Two new attachments.
x-server.log - pf said this during the x run
x.pcap - pcap taken on the client side during x run

I got no state errors on the client. Both server and client run 6-CURRENT
from yesterday.

> 
> They didn't make it to the Mailinglist - I am afraid. Can you upload it 
> somewhere or try to resend it via private mail? I'd be very interested.
At least you should have them now, sorry but I got nowhere to host them.

-- 
Pawel
-------------- next part --------------
Nov 21 20:41:50 <kern.crit> darkstar kernel: pf: BAD state: TCP 192.168.1.10:20 192.168.1.10:20 192.168.1.200:64383 [lo=133627114 high=133627802 win=33304 modulator=0 wscale=1] [lo=2384214636 high=2384281244 win=33304 modulator=0 wscale=1] 4:4 A seq=133627114 ack=2384214636 len=1448 ackskew=0 pkts=209:126 dir=out,fwd
Nov 21 20:41:50 <kern.crit> darkstar kernel: pf: State failure on: 1       |    
-------------- next part --------------
Nov 21 20:46:15 <kern.crit> darkstar kernel: pf: BAD state: TCP 192.168.1.10:20 192.168.1.10:20 192.168.1.200:61852 [lo=1505768606 high=1505769294 win=33304 modulator=0 wscale=1] [lo=3440585642 high=3440652250 win=33304 modulator=0 wscale=1] 4:4 A seq=1505768606 ack=3440585642 len=1448 ackskew=0 pkts=211:122 dir=out,fwd
Nov 21 20:46:15 <kern.crit> darkstar kernel: pf: State failure on: 1       |