From: martin f krafft <madduck@madduck.net>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: 2.6 IPsec (Kame) appears to be working, but it isn't
Date: Tue, 6 Jan 2004 18:12:36 +0100 [thread overview]
Message-ID: <20040106171236.GA3068@piper.madduck.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2049 bytes --]
Hi all,
I am not sure this is the best place to ask, but I don't want to
feel the *BSD wrath against Linux at kame.net, and I could not find
a mailing list for Linux IPsec, so please feel free to point me
elsewhere, but don't shoot, okay?
I configured two 2.6.0 hosts to do simple manually keyed transport
IPsec, just like Ralf (thanks!) wrote at www.ipsec-howto.org. When
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:
wall:~# ping 10.201.23.21
PING 10.201.23.21 (10.201.23.21) from 10.201.165.118 : 56(84) bytes of data.
--- 10.201.23.21 ping statistics ---
19 packets transmitted, 0 received, 100% loss, time 17997ms
The same applies to normal IP packets (e.g. TCP port 25):
10.201.165.118 > 10.201.23.21:
AH(spi=0x00000200,seq=0x2e): ESP(spi=0x00000201,seq=0x2e) (DF)
10.201.23.21 > 10.201.165.118:
AH(spi=0x00000300,seq=0x7): ESP(spi=0x00000301,seq=0x7) (DF)
10.201.165.118 > 10.201.23.21:
AH(spi=0x00000200,seq=0x2f): ESP(spi=0x00000201,seq=0x2f) (DF)
10.201.23.21 > 10.201.165.118:
AH(spi=0x00000300,seq=0x8): ESP(spi=0x00000301,seq=0x8) (DF)
10.201.23.21 > 10.201.165.118:
AH(spi=0x00000300,seq=0x9): ESP(spi=0x00000301,seq=0x9) (DF)
10.201.23.21 > 10.201.165.118:
AH(spi=0x00000300,seq=0xa): ESP(spi=0x00000301,seq=0xa) (DF)
Would you agree that this is weird? What am I doing wrong?
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
"i love deadlines. i like the whooshing
sound they make as they fly by."
-- douglas adams
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-01-06 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 17:12 martin f krafft [this message]
2004-01-06 18:14 ` [solved] " martin f krafft
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=20040106171236.GA3068@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®