netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Swanson <swanson@ukfsn.org>
To: netdev@vger.kernel.org
Subject: IPSEC IPV4 Tunnel Requires IPV6 WIth 2.6.25?
Date: Thu, 15 May 2008 21:09:42 +0100	[thread overview]
Message-ID: <1210882182.9684.27.camel@zeus.local> (raw)

Hi. Usual non-subscriber CC replies request please.

There is a problem with 2.6.25(.4) using IPSEC on ipv4. You seem to need
to have ipv6 available otherwise a protocol not supported error is
returned when trying to set a Security Association Database. I'm using
setkey on a file but another user on the ipsec-tools-devel list reported
the same issue using racoon.

http://marc.info/?l=ipsec-tools-devel&m=121015164014761&w=2

So with modules loaded you expect to work.

$ lsmod
  Module                  Size  Used by
  authenc                 5056  0 
  ah4                     4672  0 
  esp4                    5824  0 
  aead                    5824  2 authenc,esp4
  xfrm4_mode_tunnel       2176  20

A static file with tunnel configuration for laptop to desktop over open
wireless not running WEP/WPA.

$ head -n 12 /etc/ipsec.conf
  #!/usr/sbin/setkey -f
  
  flush;
  spdflush;
  
  add 1.1.1.1 2.2.2.2 esp 0x500 -m tunnel
  -E rijndael-cbc 0x...
  -A hmac-sha1 0x...;
  
  add 2.2.2.2 1.1.1.1 esp 0x501 -m tunnel
  -E rijndael-cbc 0x...
  -A hmac-sha1 0x...;

You get protocol not supported error.

$ setkey -f /etc/ipsec.conf
  The result of line 8: Protocol not supported.
  The result of line 12: Protocol not supported.

But after modprobing ipv6 which automatically pulls
in xfrm6_mode_tunnel, setkey starts working and I can communicate via
IPSEC.

$ lsmod
  Module                  Size  Used by
  xfrm6_mode_tunnel       2048  4 
  ipv6                  217444  10 xfrm6_mode_tunnel
  authenc                 5056  4 
  ah4                     4672  0 
  esp4                    5824  4 
  aead                    5824  2 authenc,esp4
  xfrm4_mode_tunnel       2176  28

It really shouldn't need ipv6. Full kernel config, lsmod before and
after modprobing ipv6 are available at below URL's.

http://www.swanson.ukfsn.org/ipsec/config
http://www.swanson.ukfsn.org/ipsec/lsmod-post-modprobe-ipv6
http://www.swanson.ukfsn.org/ipsec/lsmod-pre-modprobe-ipv6

-- 
Alan.

"One must never be purposelessnessnesslessness."

             reply	other threads:[~2008-05-15 20:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 20:09 Alan Swanson [this message]
2008-05-21 12:01 ` IPSEC IPV4 Tunnel Requires IPV6 WIth 2.6.25? Kazunori MIYAZAWA
2008-05-21 12:17   ` Kazunori MIYAZAWA
2008-05-21 20:18     ` Alan Swanson
2008-05-21 20:28       ` 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=1210882182.9684.27.camel@zeus.local \
    --to=swanson@ukfsn.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;
as well as URLs for NNTP newsgroup(s).