All of lore.kernel.org
 help / color / mirror / Atom feed
From: martin f krafft <madduck@madduck.net>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: [solved] 2.6 IPsec (Kame) appears to be working, but it isn't
Date: Tue, 6 Jan 2004 19:14:48 +0100	[thread overview]
Message-ID: <20040106181448.GA7684@piper.madduck.net> (raw)
In-Reply-To: <20040106171236.GA3068@piper.madduck.net>

[-- Attachment #1: Type: text/plain, Size: 989 bytes --]

also sprach martin f krafft <madduck@madduck.net> [2004.01.06.1812 +0100]:
> I now ping one end from the other, tcpdump reports successful packet
> exchanges on both sides:
> 
>   10.201.165.118 > 10.201.23.21:
>     AH(spi=0x00000200,seq=0x2d): ESP(spi=0x00000201,seq=0x2d) (DF)
>   10.201.23.21 > 10.201.165.118:
>     AH(spi=0x00000300,seq=0x6): ESP(spi=0x00000301,seq=0x6)
> 
> However, the ping application at 10.201.165.118 sees none of the
> replies:

This was (of course) my bad. One of the AH keys was incorrect.

I guess I should first learn cut'n'paste before learning IPsec
and/or bothering y'all.

Sorry.

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
 
"good advice is something a man gives
 when he is too old to set a bad example.
                                                  -- la rouchefoucauld

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-01-06 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06 17:12 2.6 IPsec (Kame) appears to be working, but it isn't martin f krafft
2004-01-06 18:14 ` martin f krafft [this message]

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=20040106181448.GA7684@piper.madduck.net \
    --to=madduck@madduck.net \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.