From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: davem@redhat.com
Cc: jan.oravec@6com.sk, netdev@oss.sgi.com
Subject: Re: IPv6/sparc64: icmp port unreachable corruption
Date: Tue, 11 Nov 2003 01:06:53 -0600 (CST) [thread overview]
Message-ID: <20031111.010653.76483304.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20031110214603.0057e365.davem@redhat.com>
In article <20031110214603.0057e365.davem@redhat.com> (at Mon, 10 Nov 2003 21:46:03 -0800), "David S. Miller" <davem@redhat.com> says:
> > 13:17:47.191547 3ffe:80ee:3bd:0:a00:20ff:fec7:a192 > 3ffe:80ee:a:0:201:3ff:fed5:bd1e: [|icmp6] (len 72, hlim 62)
> > 0x0000 6000 0000 0048 3a3e 3ffe 80ee 03bd 0000 ....H:>?.......
> > 0x0010 0a00 20ff fec7 a192 3ffe 80ee 000a 0000 ........?.......
> > 0x0020 0201 03ff fed5 bd1e 0104 aa7c 0000 0000 ...........|....
> > 0x0030 0000 0064 0000 0000 0100 0000 0100 0000 ...d............
> > 0x0040 aaaa aaaa aaaa aaaa 9680 c00b c622 7fec ............."..
> > 0x0050 aaaa aaaa aaaa aaaa 9680 c00b c622 7ffc ............."..
> > 0x0060 aaaa aaaa 0000 0000 8a10 2000 04c2 8049 ...............I
>
> What specifically about this packet makes you think it is corrupted?
:
> So why does tcpdump not say that this is "udp port XXX unreachable"
> like it does for the x86 generated packet.
>
> Incorrect checksum or corrupted payload after the icmp6 header?
0x0030- should be the copy of the original packet.
it is corrupted.
--
Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@linux-ipv6.org>
GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA
next prev parent reply other threads:[~2003-11-11 7:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-09 12:28 IPv6/sparc64: icmp port unreachable corruption Jan Oravec
2003-11-09 13:25 ` Jan Oravec
2003-11-09 13:39 ` Jan Oravec
2003-11-09 14:37 ` Jan Oravec
2003-11-11 5:46 ` David S. Miller
2003-11-11 7:06 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2003-11-11 22:26 ` Jan Oravec
2003-11-11 23:13 ` David S. Miller
2003-11-12 0:41 ` Jan Oravec
2003-11-12 9:26 ` David S. Miller
2003-11-12 15:14 ` Jan Oravec
2003-11-12 22:40 ` 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=20031111.010653.76483304.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=davem@redhat.com \
--cc=jan.oravec@6com.sk \
--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).