From: Daniil Stolnikov <danila.st@mail.ru>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
<linux-crypto@vger.kernel.org>,
<linux-security-module@vger.kernel.org>, <davem@davemloft.net>,
<adobriyan@gmail.com>, <peter.p.waskiewicz.jr@intel.com>,
<herbert@gondor.apana.org.au>
Subject: Re: Add IPSec IP Range in Linux kernel
Date: Wed, 9 Nov 2011 10:32:07 +0800 [thread overview]
Message-ID: <552673196.20111109103207@mail.ru> (raw)
In-Reply-To: <20111108.204253.891598837549584662.davem@davemloft.net>
> Like I said, if you want address ranges, ask the userland IPSEC daemon
> authors to synthesize it.
In this letter, the mailing list http://marc.info/?l=strongswan-users&m=130613736616488&w=4 strongswan-users say that their product has support for IP ranges, but the stack of Linux is based on network masks. So I do not understand how this would work without the support at the kernel level? How will coordination of policies?
next prev parent reply other threads:[~2011-11-09 2:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 3:10 Add IPSec IP Range in Linux kernel Daniil Stolnikov
2011-11-08 6:24 ` Peter P Waskiewicz Jr
2011-11-08 10:51 ` Daniil Stolnikov
2011-11-08 12:08 ` Alexey Dobriyan
2011-11-08 14:24 ` Daniil Stolnikov
2011-11-08 17:16 ` David Miller
2011-11-09 1:36 ` Daniil Stolnikov
2011-11-09 1:42 ` David Miller
2011-11-09 1:54 ` Herbert Xu
2011-11-09 2:43 ` Daniil Stolnikov
2011-11-09 2:32 ` Daniil Stolnikov [this message]
2011-11-09 3:27 ` Herbert Xu
2011-11-09 7:25 ` Daniil Stolnikov
[not found] ` <E1RNhE5-0005rf-00.danila-st-mail-ru@f105.mail.ru>
2011-11-08 17:15 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=552673196.20111109103207@mail.ru \
--to=danila.st@mail.ru \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).