From: "Christopher K. Johnson" <ckjohnson@gwi.net>
To: netdev@oss.sgi.com
Subject: IPsec tunnel mode bug - malformed, misaddressed packets
Date: Sun, 17 Oct 2004 07:52:21 -0400 [thread overview]
Message-ID: <41725CF5.2010606@gwi.net> (raw)
There is an ipsec bug in FC2 kernel 2.6.8-1.521 for ipsec tunnel mode.
I have proven with a packet trace that some packets are
misaddressed. Specifically it constructs a packet of the form:
IP header1 | AH header | IP header2 | ESP
The IP header1 has an incorrect destination address of the host in the
remote tunneled subnet instead of the remote vpn partner, whereas IP
header2 has the correct destination address of the remote vpn partner.
For an host in local ipsec subnet contacting a web server in remote
ipsec subnet the initial syn and response of syn,ack are tunnelled
successfuly, but the encrypted ack goes out malformed as indicated above,
thus is never delivered.
Packet trace and setkey config are attached to bugzilla entry at
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=132832
Your help in resolving this bug so ipsec is usable would be appreciated greatly.
Chris
next reply other threads:[~2004-10-17 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 11:52 Christopher K. Johnson [this message]
2004-10-18 1:08 ` IPsec tunnel mode bug - malformed, misaddressed packets Herbert Xu
2004-10-18 23:17 ` Christopher K. Johnson
2004-10-18 23:49 ` Herbert Xu
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=41725CF5.2010606@gwi.net \
--to=ckjohnson@gwi.net \
--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).