netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: netdev@oss.sgi.com
Subject: ipsec, nat-t, iproute2?
Date: Fri, 30 Jul 2004 19:07:26 +0200	[thread overview]
Message-ID: <20040730170726.GA5144@outpost.ds9a.nl> (raw)

Hi people,

I'm once again trying to get a hang of the state of ipsec in linux, and I
have some questions.

1) One can configure ipsec over netlink (XFRM_USER), is this the preferred
interface? Is it documented somehwere, or is there some source which uses
this interface? Alternatively, is PFKEY considered deprecated?

2) I hear people are working on iproute so it can use XFRM_USER, is this
code available somewhere?

3) NAT-Traversal, how does one set this up either using setkey,
iproute2+stuff, or XFRM_USER? Is it supposed to work right now?
Is NAT-T 'UDP_ENCAP_ESPINUDP'?

Thanks. What I'll figure out from these questions I'll document.

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO

             reply	other threads:[~2004-07-30 17:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 17:07 bert hubert [this message]
2004-07-30 18:12 ` ipsec, nat-t, iproute2? bert hubert
2004-07-30 18:55 ` James Morris
2004-07-30 22:38   ` (udp-en/decap broken in 2.6.8-rc2?) " bert hubert
2004-07-31  7:50     ` Herbert Xu
2004-07-31  8:34       ` bert hubert
2004-07-31 10:32         ` Herbert Xu
2004-07-31 11:20           ` bert hubert
2004-07-31 11:52             ` Herbert Xu
2004-07-31 12:18               ` bert hubert
2004-07-31 13:08                 ` [IPSEC PATCH] missing break in UDP decap code " bert hubert
2004-07-31 19:32                   ` Herbert Xu
2004-08-01  6:53                     ` David S. 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=20040730170726.GA5144@outpost.ds9a.nl \
    --to=ahu@ds9a.nl \
    --cc=netdev@oss.sgi.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).