From: Valentijn Sessink <valentyn+netfilter-users@nospam.openoffice.nl>
To: netfilter@lists.netfilter.org
Subject: more IPsec NAT troubles
Date: Sat, 31 Jan 2004 18:52:45 +0100 [thread overview]
Message-ID: <20040131175245.GA21239@openoffice.nl> (raw)
Hello list,
As a side note, but relevant in the light of the recent IPsec/NAT
interoperability, I found another bug in the IPsec implementation.
2.6 + IPsec causes problems for connections that need fragmentation. My
setup:
desktop masq'ing $router
2.4.24+ipsec 2.6.1
10.x.y.25--------10.x.y.1 MASQ a.b.c.d ---> Internet
Now if a packet from the Internet larger than 1444 bytes arrives (which is
perfectly legal), $router will send the rather odd response "icmp
a.b.c.d unreachable, need to frag (1444 bytes)". So you get the $router tell
that $router is unreachable when a packet reaches the $router.
ip_output.c says:
if (skb->len > mtu) {
icmp_send(skb, ICMP_DEST_UNREACH, ICMP_FRAG_NEEDED, htonl(mtu));
ret = -EMSGSIZE;
So if I understand this correctly, the IPsec tunnel relies on the end to end
MTU detection and simply drops packets when they're too large to
encapsulate. However, in a masq'ing/IPsec combination, this won't work, as
there is no "end to end". The fragmentation is needed for a local process
(namely after de-masq'ing the packet when the kernel finds out it needs to
encrypt the packet) and I think the FRAG_NEEDED is illegal here.
I sent this to linux-net where it's probably more appropriate. (I hope my
e-mail reaches the list, as anti spam measures here and there are starting
to prevent any communication)
V.
--
http://www.openoffice.nl/ Open Office - Linux Office Solutions
Valentijn Sessink valentyn+sessink@nospam.openoffice.nl
reply other threads:[~2004-01-31 17:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040131175245.GA21239@openoffice.nl \
--to=valentyn+netfilter-users@nospam.openoffice.nl \
--cc=netfilter@lists.netfilter.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