From: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
To: Daniil Stolnikov <danila.st@mail.ru>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: Add IPSec IP Range in Linux kernel
Date: Mon, 07 Nov 2011 22:24:25 -0800 [thread overview]
Message-ID: <1320733465.21617.4.camel@ppwaskie-mobl2> (raw)
In-Reply-To: <92909814.20111108111036@mail.ru>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
On Mon, 2011-11-07 at 19:10 -0800, Daniil Stolnikov wrote:
> Hello!
>
> Found that the stack IPSec in Linux does not support any IP range. Many people ask this question. The archives say strongswan said that their daemon supports a range, but the Linux IPSec stack supports only the subnets. I am writing to you to implement support for IP range in Linux. I think that a lot more people will appreciate this innovation.
It'd be even better if you could write a patch for us to review.
Cheers,
-PJ
>
> Regards
> Daniil Stolnikov.
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
LAN Access Division, Intel Corporation
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4394 bytes --]
next prev parent reply other threads:[~2011-11-08 6:24 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 [this message]
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
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=1320733465.21617.4.camel@ppwaskie-mobl2 \
--to=peter.p.waskiewicz.jr@intel.com \
--cc=danila.st@mail.ru \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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