On Sat, Nov 15, 2008 at 6:17 PM, Petr Janda <[EMAIL PROTECTED]> wrote: >> window scaling shift 0 is allowed. It just mean we support window >> scaling, but the shift is 0. >> From the dump, it looks like the other side is a Linux box. >> >> > Could Sephe give a suggestion about what is the problem here and how I >> > can solve it? >> >> As Joerg has suggested, window scaling option may be problematic with >> pf. You could try set net.inet.tcp.rfc1323 to 0 > > > Here is another dump this time with rfc1323, sack and smartsack disabled. Do > you notice something weird here?
17:48:34.875003 IP 203.16.214.214.41558 > 202.76.131.108.25: P 91:145(54) ack 218 win 49640 /* 17:48:34.915642 IP 202.76.131.108.25 > 203.16.214.214.41558: P 218:269(51) ack 145 win 58400 */ 17:48:34.952747 IP 203.16.214.214.41558 > 202.76.131.108.25: P 7445:8337(892) ack 269 win 49640 Several segments (203.16.214.214 -> 202.76.131.108) are never seen by the driver. 17:48:34.952792 IP 202.76.131.108.25 > 203.16.214.214.41558: . ack 145 win 58400 Application seems to use 5min timeout. The question is why 203.16.214.214 did not rexmit? 17:53:34.930919 IP 202.76.131.108.25 > 203.16.214.214.41558: P 269:325(56) ack 145 win 58400 17:53:34.931606 IP 202.76.131.108.25 > 203.16.214.214.41558: F 325:325(0) ack 145 win 58400 Best Regards, sephe -- Live Free or Die
