From owner-freebsd-net@freebsd.org  Sat Mar 11 22:16:28 2017
Return-Path: <owner-freebsd-net@freebsd.org>
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 08CD7D0884F
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Sat, 11 Mar 2017 22:16:28 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C12E2D0F
 for <freebsd-net@freebsd.org>; Sat, 11 Mar 2017 22:16:27 +0000 (UTC)
 (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1cmpJD-0003KO-Aw; Sun, 12 Mar 2017 01:16:19 +0300
Date: Sun, 12 Mar 2017 01:16:19 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Hooman Fazaeli <hoomanfazaeli@gmail.com>
Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject: Re: ipsec with ipfw
Message-ID: <20170311221619.GU15630@zxy.spb.ru>
References: <58C46AE0.7050408@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <58C46AE0.7050408@gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/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: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Mar 2017 22:16:28 -0000

On Sun, Mar 12, 2017 at 12:53:44AM +0330, Hooman Fazaeli wrote:

> Hi,
> 
> As you know the ipsec/setkey provide limited syntax to define security
> policies: only a single subnet/host, protocol number and optional port
> may be used to specify traffic's source and destination.
> 
> I was thinking about the idea of using ipfw as the packet selector for ipsec,
> much like it is used with dummeynet. Something like:
> 
> ipfw add 100 ipsec 2 tcp from <lan-table> to <remote-servers-table> 80,443,110,139
> 
> What do you think? Are you interested in such a feature?
> Is it worth the effort? What are the implementation challenges?

security policies is subject of ike protocol exchange, do you plened
to extend this protocol too?