Hello everybody, I fully agree with Daniel, here we've correct values. May i suggest (in order to clarify situation) we use the same host/IP during exchanges (because it's a bit difficult to diagnose what's happening0) :-)
Precedent message was between OpenBSD/Linux (IP were 10.137.8.104 -> 10.137.9.55) and there were bad mss 10.137.8.104.30290 > 10.137.9.55.80: S 568783555:568783555(0) win 16384 <mss 1460> Now we're using not only OpenBSD's tcpdump but obviously different IPs (and good mss) 192.168.133.200.9901 > 192.168.133.1.80: S [tcp sum ok] 1790495358:1790495358(0) win 16384 <mss 1400> So, are they the same hosts (with just different IP) ? Please note i may try to reproduce a lot of things, i just need to know about them... :-) With regards, Jean-Philippe. On Mon, 9 Jun 2008 10:54:44 -0600 "Daniel Melameth" <[EMAIL PROTECTED]> wrote: > On Mon, Jun 9, 2008 at 9:06 AM, B A <[EMAIL PROTECTED]> wrote: > > bash-3.2# pfctl -sr > > scrub all no-df random-id max-mss 1400 fragment reassemble > > pass in quick all flags S/SA keep state > > pass out quick all flags S/SA keep state > > > Ok. Here is openbsd tcpdump. But I still see len 1440 packets. > > > > 03:57:54.035986 192.168.133.200.9901 > 192.168.133.1.80: S [tcp sum > > ok] 1790495358:1790495358(0) win 16384 <mss > > 1400,nop,nop,sackOK,nop,wscale 0,nop,nop,timestamp 3743718606 0> > > You might want to read up on packet structures as this is working as > expected. The header of a TCP packet is normally 40 bytes--so you're > seeing a maximum MSS of 1400 bytes and an MTU of 1440 bytes.
