From: bert hubert <ahu@ds9a.nl>
To: netdev@oss.sgi.com
Subject: ip6sec broken *differently* in 2.5.66 :-)
Date: Tue, 25 Mar 2003 12:27:05 +0100 [thread overview]
Message-ID: <20030325112705.GA9793@outpost.ds9a.nl> (raw)
Alexey, thanks for the work on ip6sec but it still does slightly the wrong
thing here.
snapcount:~# ping6 -s 1406 deef.ds9a.nl
43.14 snapcount.ipv6.ds9a.nl > deef.ds9a.nl:
AH(spi=0x00003d54,sumlen=16,seq=0x1e7): ESP(spi=0x00003d55,seq=0x1e7)
[hlim 0] (len 1456)
43.14 deef.ds9a.nl > snapcount.ipv6.ds9a.nl: icmp6:
echo reply (len 1414, hlim 64)
If I make the ping one byte bigger, nothing gets sent out! This goes on
until ping6 -s 1452, and then suddenly with ping6 -s 1453:
43.57 snapcount.ipv6.ds9a.nl > deef.ds9a.nl:
AH(spi=0x00003d54,sumlen=16,seq=0x327): ESP(spi=0x00003d55,seq=0x327)
[hlim 0] (len 64)
Like the first segment didn't make it. If I further increase the pingsize to
-s 1455, this happens:
34.02 snapcount.ipv6.ds9a.nl > deef.ds9a.nl:
AH(spi=0x00003d54,sumlen=16,seq=0x409): ESP(spi=0x00003d55,seq=0x409)
[hlim 0] (len 72)
Anything I can do to help, let me know.
Thanks.
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
http://netherlabs.nl Consulting
reply other threads:[~2003-03-25 11:27 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=20030325112705.GA9793@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--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).