From: bert hubert <ahu@ds9a.nl>
To: James Morris <jmorris@redhat.com>
Cc: netdev@oss.sgi.com
Subject: (udp-en/decap broken in 2.6.8-rc2?) Re: ipsec, nat-t, iproute2?
Date: Sat, 31 Jul 2004 00:38:09 +0200 [thread overview]
Message-ID: <20040730223808.GA12660@outpost.ds9a.nl> (raw)
In-Reply-To: <Xine.LNX.4.44.0407301453470.20521-100000@dhcp83-76.boston.redhat.com>
On Fri, Jul 30, 2004 at 02:55:19PM -0400, James Morris wrote:
> PF_KEY is not deprecated, it's an IETF standard and required for
> compliance & compatibility. XFRM_USER is simply the native Linux
> interface.
Ok, thanks. I've gotten to the point where I can configure nat-t over XFRM,
however, I find that it does not work.
The encoding looks fine but the receiving side does not appear to listen:
00:34:09.491228 IP 192.168.1.4.4500 > 10.0.0.3.4500: UDP, length: 88
00:34:09.492290 IP 10.0.0.3 > 192.168.1.4: icmp 124: 10.0.0.3 udp port 4500
unreachable
00:34:10.492245 IP 192.168.1.4.4500 > 10.0.0.3.4500: UDP, length: 88
00:34:10.493332 IP 10.0.0.3 > 192.168.1.4: icmp 124: 10.0.0.3 udp port 4500
unreachable
00:34:11.493090 IP 192.168.1.4.4500 > 10.0.0.3.4500: UDP, length: 88
00:34:11.494337 IP 10.0.0.3 > 192.168.1.4: icmp 124: 10.0.0.3 udp port 4500
unreachable
This is the setkey configuration I use on 10.0.0.3:
#!/usr/sbin/setkey -f
flush;
spdflush;
add 192.168.1.4 10.0.0.3 esp-udp 10.0.0.3 34501
-E 3des-cbc "123456789012123456789012";
spdadd 192.168.1.4 10.0.0.3 icmp -P in ipsec
esp/transport//require;
And on the other side (192.168.1.4):
#!/usr/sbin/setkey -f
flush;
spdflush;
add 192.168.1.4 10.0.0.3 esp-udp 192.168.1.4 34501
-E 3des-cbc "123456789012123456789012";
spdadd 192.168.1.4 10.0.0.3 icmp -P out ipsec
esp/transport//require;
I've toyed a bit with the IP address after esp-udp, not sure what it does.
Thanks.
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2004-07-30 22:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 17:07 ipsec, nat-t, iproute2? bert hubert
2004-07-30 18:12 ` bert hubert
2004-07-30 18:55 ` James Morris
2004-07-30 22:38 ` bert hubert [this message]
2004-07-31 7:50 ` (udp-en/decap broken in 2.6.8-rc2?) " 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=20040730223808.GA12660@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=jmorris@redhat.com \
--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).