From owner-freebsd-net@FreeBSD.ORG Fri Jul 11 10:25:32 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3E140B71 for ; Fri, 11 Jul 2014 10:25:32 +0000 (UTC) Received: from nijmegen.renzel.net (mx1.renzel.net [195.243.213.130]) by mx1.freebsd.org (Postfix) with ESMTP id F244A2875 for ; Fri, 11 Jul 2014 10:25:31 +0000 (UTC) Received: from dublin.vkf.isb.de.renzel.net (unknown [10.0.0.80]) by nijmegen.renzel.net (smtpd) with ESMTP id A44EC14148B1 for ; Fri, 11 Jul 2014 12:24:27 +0200 (CEST) Received: from asbach.renzel.net (unknown [10.2.0.7]) by dublin.vkf.isb.de.renzel.net (Postfix) with ESMTP id D0F061A0C06 for ; Fri, 11 Jul 2014 12:24:31 +0200 (CEST) Content-Type: text/plain; charset="ISO-8859-1" From: Nils Beyer Organization: VKF Renzel GmbH Date: Fri, 11 Jul 2014 12:24:31 +0200 User-Agent: KNode/4.12.5 Content-Transfer-Encoding: 7Bit Subject: Re: Multipath TCP for FreeBSD v0.4 To: freebsd-net@freebsd.org References: <513CB9AF.3090409@swin.edu.au> <53BF8945.3000802@swin.edu.au> Lines: 58 MIME-Version: 1.0 X-Virus-Scanned: clamav-milter 0.98 at nijmegen.renzel.net X-Virus-Status: Clean X-Spam-Status: No, score=-6.5 required=7.0 tests=BAYES_00,MISSING_MID, UNPARSEABLE_RELAY autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on nijmegen.renzel.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2014 10:25:32 -0000 Hi Nigel, Nigel Williams wrote: > A new v0.4 patch is available at [1]. [...] Thanks a lot for publishing the latest patch. Already tried it on two phyiscal machines with directly connected NICs. "iperf" looks nice: =============================================================================== #iperf -c 10.255.255.11 -i 1 ------------------------------------------------------------ Client connecting to 10.255.255.11, TCP port 5001 TCP window size: 32.5 KByte (default) ------------------------------------------------------------ [ 3] local 10.255.255.10 port 40171 connected with 10.255.255.11 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0- 1.0 sec 167 MBytes 1.40 Gbits/sec [ 3] 1.0- 2.0 sec 171 MBytes 1.43 Gbits/sec [ 3] 2.0- 3.0 sec 171 MBytes 1.44 Gbits/sec [ 3] 3.0- 4.0 sec 171 MBytes 1.44 Gbits/sec [ 3] 4.0- 5.0 sec 171 MBytes 1.44 Gbits/sec [ 3] 5.0- 6.0 sec 169 MBytes 1.41 Gbits/sec [ 3] 6.0- 7.0 sec 168 MBytes 1.41 Gbits/sec [ 3] 7.0- 8.0 sec 169 MBytes 1.41 Gbits/sec [ 3] 8.0- 9.0 sec 168 MBytes 1.41 Gbits/sec [ 3] 9.0-10.0 sec 171 MBytes 1.43 Gbits/sec [ 3] 0.0-10.0 sec 1.66 GBytes 1.42 Gbits/sec =============================================================================== TCP networking is rather unstable after some "iperf" executions. So that new SSH connections aren't possible anymore. Everything more complex than "iperf" - like NFS and FTP usage - leads to a kernel panic (page fault). Do you want any crash dumps? If yes, where do you want them to be uploaded? FWIW: I haven't set up any special routings or PF rules at all: =============================================================================== MPTCP1 ------ ifconfig_em1="10.255.255.10/8 -tso" ifconfig_em0="192.168.1.1/24 -tso" ifconfig_em2="192.168.2.1/24 -tso" MPTCP2 ------ ifconfig_em1="10.255.255.11/8 -tso" ifconfig_em0="192.168.1.2/24 -tso" ifconfig_em2="192.168.2.2/24 -tso" =============================================================================== Thanks for all your work and regards, Nils