From owner-freebsd-net@freebsd.org Fri Oct 23 05:48:06 2015 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53587A1677D for ; Fri, 23 Oct 2015 05:48:06 +0000 (UTC) (envelope-from njwilliams@swin.edu.au) Received: from gpo1.cc.swin.edu.au (gpo1.cc.swin.edu.au [136.186.1.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C9633CF7 for ; Fri, 23 Oct 2015 05:48:05 +0000 (UTC) (envelope-from njwilliams@swin.edu.au) Received: from [136.186.229.154] (nwilliams-laptop.caia.swin.edu.au [136.186.229.154]) by gpo1.cc.swin.edu.au (8.14.3/8.14.3) with ESMTP id t9N5lwHf016645; Fri, 23 Oct 2015 16:47:59 +1100 Subject: Re: MPTCP for FreeBSD repository on BitBucket/v0.51 update To: George Neville-Neil References: <562466AA.7020707@swin.edu.au> <137EE92F-7611-402D-874F-37AA627F41CA@neville-neil.com> Cc: freebsd-net@freebsd.org From: Nigel Williams Message-ID: <5629C9BF.2030902@swin.edu.au> Date: Fri, 23 Oct 2015 16:46:39 +1100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <137EE92F-7611-402D-874F-37AA627F41CA@neville-neil.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 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, 23 Oct 2015 05:48:06 -0000 Hi George, > > Very nice! Just wondering how you're testing this out. I've been > working on a lot of networking > tests and I'm sure MPTCP introduces some interesting complications. > Right now the tests are quite simple - based off the shell scripts and topology here: https://bitbucket.org/nw-swin/caia-mptcp-files/src These are mostly quick and dirty tests to catch regressions (I'm still making some fairly broad changes to the implementation). They provide basic MP connections and some dummynet control to adjust the link characteristics. I don't yet have anything where I can easily script-in topology changes, bring links up and down mid-connection, introduce cross traffic, etc... but the plan is to move to that kind of set up. And it's probably worth mentioning I've just been running my tests in VMs, though I'd like to run tests on hardware once I squash some of the stability issues. cheers, nigel