On Mon, Oct 22, 2007 at 09:59:02AM +0300, Joakim Koskela wrote:
>
> Ok, this really sounds like a good development. Do you think it could make it
> in time for 2.6.24?
Sorry, I think it's 2.6.25 material.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[EMAIL
On Friday 19 October 2007 17:22:22 Herbert Xu wrote:
>
> Please hold onto this. I've got a more generic version of this
> that doesn't duplicate the inter-family logic between BEET mode
> and tunnel mode.
>
> Instead I've created a generic function that reads info from the
> inner header and puts
Please fix up these whitespace errors in your patch, thank you:
+ git apply --check --whitespace=error-all diff
Space in indent is followed by a tab.
diff:329: if (x->sel.family == AF_INET) {
Space in indent is followed by a tab.
diff:330: x->props.header_len +
Joakim Koskela <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Here's an updated version of the patch adding support for ipv4/ipv6
> interfamily addressing for the ipsec BEET (Bound End-to-End Tunnel)
> mode, as specified by the ietf draft found at:
>
> http://www.ietf.org/internet-drafts/draft-nikander-esp
Hi,
Here's an updated version of the patch adding support for ipv4/ipv6
interfamily addressing for the ipsec BEET (Bound End-to-End Tunnel)
mode, as specified by the ietf draft found at:
http://www.ietf.org/internet-drafts/draft-nikander-esp-beet-mode-07.txt
The previous implementation required
