From owner-freebsd-net@FreeBSD.ORG  Sun Apr  5 21:37:27 2009
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5D07A106566C
	for <freebsd-net@freebsd.org>; Sun,  5 Apr 2009 21:37:27 +0000 (UTC)
	(envelope-from sthaug@nethelp.no)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33])
	by mx1.freebsd.org (Postfix) with SMTP id 60FB78FC17
	for <freebsd-net@freebsd.org>; Sun,  5 Apr 2009 21:37:26 +0000 (UTC)
	(envelope-from sthaug@nethelp.no)
Received: (qmail 30249 invoked from network); 5 Apr 2009 21:10:44 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33)
	by bizet.nethelp.no with SMTP; 5 Apr 2009 21:10:44 -0000
Date: Sun, 05 Apr 2009 23:10:44 +0200 (CEST)
Message-Id: <20090405.231044.74688369.sthaug@nethelp.no>
To: freebsd-net@freebsd.org
From: sthaug@nethelp.no
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: IPv6 window scaling factor always 1 on initial SYN
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Apr 2009 21:37:28 -0000

On 7-STABLE, with kern.ipc.maxsockbuf=2621440, both sides set a window
scaling factor of 6 (i.e. SYN wscale 6, SYN-ACK wscale 6) using IPv4.

With the same value of kern.ipc.maxsockbuf, using IPv6, the side which
sends the initial SYN sets a window scaling factor of only 1, while
the other side sets a scaling factor of 6 in the SYN-ACK. This will
obviously limit throughput in many cases.

In both cases net.inet.tcp.rfc1323=1.

Anybody know why IPv6 behaves differently here?

tcpdump example:

22:20:37.282415 IP 193.75.4.50.53981 > 193.75.110.66.5555: S 1580765626:1580765626(0) win 65535 <mss 1460,nop,wscale 6,sackOK,timestamp 661320721 0>
22:20:37.282442 IP 193.75.110.66.5555 > 193.75.4.50.53981: S 1408884711:1408884711(0) ack 1580765627 win 65535 <mss 1460,nop,wscale 6,sackOK,timestamp 1581013561 661320721>

22:21:49.749586 IP6 2001:8c0:9a00:1::2.53983 > 2001:8c0:8500:1::2.5555: S 565631163:565631163(0) win 65535 <mss 1440,nop,wscale 1,sackOK,timestamp 661393190 0>
22:21:49.749633 IP6 2001:8c0:8500:1::2.5555 > 2001:8c0:9a00:1::2.53983: S 627173961:627173961(0) ack 565631164 win 65535 <mss 1440,nop,wscale 6,sackOK,timestamp 8

Steinar Haug, Nethelp consulting, sthaug@nethelp.no