netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Michal Ruzicka <michal.ruzicka@comstar.cz>
Cc: davem@davemloft.net, kuznet@ms2.inr.ac.ru, netdev@vger.kernel.org
Subject: Re: AF_KEY extended xfrm_state selector handling
Date: Thu, 19 Oct 2006 20:59:32 -0400	[thread overview]
Message-ID: <1161305972.5034.58.camel@jzny2> (raw)
In-Reply-To: <200610191626.k9JGQ7x4014606@gateplz.comstar.cz>

On Thu, 2006-19-10 at 18:26 +0100, Michal Ruzicka wrote:
> Hello
> 
> In an effort to configure an L2TP/IPsec server on Linux capable of supporting
> multiple clients behind a single NAT device I ran into difficulties with pf_key
> protocol implementation not being able to exploit all the information
> passed to it as a SADB_EXT_ADDRESS_PROXY info. Perhaps as the original source
> suggested (/* Nobody uses this, but we try. */) this info has never been used
> before.


BTW, why not use xfrm instead? Then you dont have to worry about racoon.
Unless you care about running this in some other OS (I suspect these
OSes probably have made use of SADB_EXT_ADDRESS_PROXY so that may be a
futile effort in any case).


cheers,
jamal

PS:- Nothing stands out for me in your patch, so i have no comment; i
wasnt sure if the concept of tcp/udp port meant much to the concept of a
security association



  reply	other threads:[~2006-10-20  0:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19 17:26 AF_KEY extended xfrm_state selector handling Michal Ruzicka
2006-10-20  0:59 ` jamal [this message]
2006-10-20  8:56   ` Michal Růžička
2006-10-20  9:52     ` 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=1161305972.5034.58.camel@jzny2 \
    --to=hadi@cyberus.ca \
    --cc=davem@davemloft.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=michal.ruzicka@comstar.cz \
    --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;
as well as URLs for NNTP newsgroup(s).