From owner-freebsd-net@freebsd.org Tue Dec 27 14:10:53 2016 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 242E2C8A725; Tue, 27 Dec 2016 14:10:53 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward1p.cmail.yandex.net (forward1p.cmail.yandex.net [77.88.31.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D2C061C5B; Tue, 27 Dec 2016 14:10:52 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp2p.mail.yandex.net (smtp2p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b6:7]) by forward1p.cmail.yandex.net (Yandex) with ESMTP id 3C213206A2; Tue, 27 Dec 2016 17:10:43 +0300 (MSK) Received: from smtp2p.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2p.mail.yandex.net (Yandex) with ESMTP id 57E5C1A8005A; Tue, 27 Dec 2016 17:10:40 +0300 (MSK) Received: by smtp2p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id u0pS26SToL-AdQKnW9E; Tue, 27 Dec 2016 17:10:40 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1482847840; bh=D5EqgLa7fidsqvuF/bL8hpfr+BSutNcNsOi52eLaxq0=; h=Subject:To:References:Cc:From:Message-ID:Date:In-Reply-To; b=oI+alu6NpL1bVuQL4aJkqzp8iksqmYVgsErF0yYS2B3Bul91gxN1jPnM92OJ6dNJH /+G0P/usWMdYW4oyRHNa95HP0sO8mQU4dZQSJ/AaJA6PHSlsZ8JRfdg6EcsXgASvvf weEfreLVRqu9HRS3/ZbqiUuF0BwXAE5NiUEaWfbE= Authentication-Results: smtp2p.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0,1 0,1 0 Subject: Re: [RFC/RFT] projects/ipsec To: Jim Thompson , "Eugene M. Zheganin" References: <2bd32791-944f-2417-41e9-e0fe1c705502@FreeBSD.org> <5889f1f5-5585-95d4-beac-285dbc722b4e@norma.perm.ru> Cc: FreeBSD Current , freebsd-net From: "Andrey V. Elsukov" Message-ID: Date: Tue, 27 Dec 2016 17:10:02 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2016 14:10:53 -0000 On 27.12.2016 16:15, Jim Thompson wrote: >> In it's initial state if_ipsec allows to use only one set of >> encryption parameters (because only one sainfo anonyumous is >> possible), so at this time it doesn't allow to create multiple >> tunnels with VPN hubs that use different cipers and/or transform >> sets, but as far as I understand this is subject to change and >> Andrey is already working on a support of this feature from >> ipsec-tools IKE daemon. > > pfSense (which you mention below) is using strongswan, so when > Andrey is finished with ipsec-tools, we will need to review his > changes and see what we can do for strongswan. > > I'm looking forward to the mutliple-tunnel support, which is > required for pfSense. There are no such limits. You can create multiple VTI interfaces. The problem is in with racoon configuration restrictions. It looks like ipsec-tools project is dead, I didn't received any replies from ipsec-tools-devel mailing list. I'm not aware how to configure strongswan, so if someone will not try to do this, I don't know when I will do this. -- WBR, Andrey V. Elsukov