From: bert hubert <ahu@ds9a.nl>
To: Jon Grimm <jgrimm2@us.ibm.com>
Cc: "linux-net@vger.kernel.org" <linux-net@vger.kernel.org>,
"netdev@oss.sgi.com" <netdev@oss.sgi.com>
Subject: ip6sec MTU/fragmentation issue / Was: Re: [PATCH] Fix ip6_build_xmit bug
Date: Sat, 22 Mar 2003 20:26:04 +0100 [thread overview]
Message-ID: <20030322192604.GA3011@outpost.ds9a.nl> (raw)
In-Reply-To: <3E7BAC7E.AEC59251@us.ibm.com>
On Fri, Mar 21, 2003 at 06:21:18PM -0600, Jon Grimm wrote:
> Wanting to play a bit with v6 fragmentation I started using ping6 to
> send various message sizes. Noticed that messages of sizes just under
> where fragmentation would kick in, segfaulted in ip6_build_xmit().
Thanks, this fixes an observed issue here with segfaults in ping6, as you
described. I run 2.5.65.
There is another problem with ip6sec however where fragmentation fails.
Setting up an ip6sec connection and then sending bulk data freezes up a
connection.
ping6 -s 1500 deef.ds9a.nl -n leads to:
20:16:18.125073 2001:888:1036:0:2a0:ccff:fec8:f25c >
2001:888:1036:0:2e0:18ff:fe23:cece: AH(spi=0x00003d54,sumlen=16,seq=0xbe):
ESP(spi=0x00003d55,seq=0xbe) (len 1504, hlim 64)
20:16:18.125129 2001:888:1036:0:2a0:ccff:fec8:f25c >
2001:888:1036:0:2e0:18ff:fe23:cece: AH(spi=0x00003d54,sumlen=16,seq=0xbf):
ESP(spi=0x00003d55,seq=0xbf) (len 112, hlim 64)
and a reply:
20:16:18.125474 2001:888:1036:0:2e0:18ff:fe23:cece >
2001:888:1036:0:2a0:ccff:fec8:f25c: AH(spi=0x00005fb4,sumlen=16,seq=0x82):
ESP(spi=0x00005fb5,seq=0x82) [hlim 0] (len 160)
The reply appears to be a bit short and is possibly an ICMP error. When I
configure ip6sec only in one way, I get this reply to fragmented ICMP echo
requests:
20:22:24.445157 2001:888:1036:0:2e0:18ff:fe23:cece >
2001:888:1036:0:2a0:ccff:fec8:f25c: icmp6: parameter problem next header -
octet 6 (len 116, hlim 64)
This is probably the same packet as we see encrypted above.
Working ping6, -s 1400, looks like this:
20:18:56.820699 2001:888:1036:0:2a0:ccff:fec8:f25c >
2001:888:1036:0:2e0:18ff:fe23:cece: AH(spi=0x00003d54,sumlen=16,seq=0x142):
ESP(spi=0x00003d55,seq=0x142) (len 1456, hlim 64)
20:18:56.821912 2001:888:1036:0:2e0:18ff:fe23:cece >
2001:888:1036:0:2a0:ccff:fec8:f25c: AH(spi=0x00005fb4,sumlen=16,seq=0xce):
ESP(spi=0x00005fb5,seq=0xce) [hlim 0] (len 1456)
Both of these hosts have your patch applied. So it seems that ip6sec
fragmentation has some issues.
Thanks.
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
http://netherlabs.nl Consulting
next prev parent reply other threads:[~2003-03-22 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 0:21 [PATCH] Fix ip6_build_xmit bug Jon Grimm
2003-03-22 19:26 ` bert hubert [this message]
2003-03-23 9:22 ` 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=20030322192604.GA3011@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=jgrimm2@us.ibm.com \
--cc=linux-net@vger.kernel.org \
--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).