Re: RSTs being marked as invalid because of wrong td_maxack value

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ali Abdallah <ali.abdallah@xxxxxxxx> wrote:
> Yes, they do support timestamps, but I'm not sure if that will solve
> the problem, as the problematic out of order frame #5 has more recent
> timestamps.
> 
> 1: 703 → 2049 [ACK] Seq=1132947682 Ack=1202969688 Win=2661 Len = 0
> TSval=3506781692 TSecr=1717385629
> 
> 2: 2049 → 703 [RST, ACK] Seq=1202969688 Ack=1132949130 Win=69120 Len=0
> TSval=1717385630 TSecr=3506781692

Ok, right, I forgot we may have different clients behind NAT.



[Index of Archives]     [Netfitler Users]     [Berkeley Packet Filter]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux