Hello all--
The attached file has a handful of IPv6 packets in it. Ethereal 0.9.6 does
not display the source or destination IP address in the packet summary, nor
do the addresses show up in the ASCII decode, although they are in the
packet. FYI, Ethereal 0.9.4 decodes these packets properly.
Thanks for a great product! If you want me to help test a fix, just mail me
an installer and I'll try it out as soon as I can.
Thanks,
Tom
-----Original Message-----
From: Gerald Combs [mailto:gerald@xxxxxxxxxxxx]
Sent: Sunday, 22 September, 2002 08:55
To: Thomas Maufer
Subject: Re: who can I ask about an IPv6 display bug?
Jun-ichiro itojun Hagino was the original author of the IPv6 code, but
many other people have contributed changes over the years. Your best bet
would be to send a message to the ethereal-dev mailing list. If you have
a sample capture (even one that contains a single packet) that shows this
behavior, it would be helpful.
On Fri, 20 Sep 2002, Thomas Maufer wrote:
> Gerald--
>
> When looking at IPv6 packets with link-local addresses, the "source
> address" and "destination address" columns are both blank, and in the
> packet decode the numbers are not present, although if you click on
> "source address" you will see the correct value highlighted in the
> hex dump. I'm not sure if this also happens for non-link-local
> addresses. I'd like to report this to whomever contributed the IPv6
> decode support.
>
> Normally an IPv6 address is displayed as:
>
> "0123:4567:89AB:CDEF:FEDC:BA98:7654:3210".
>
> The document that describes all the various textual represenations
> of an IPv6 address is:
>
>
>
<http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-addr-arch-v3-10.txt>
>
> which is an updated version of RFC-2373:
>
> <http://www.ietf.org/rfc/rfc2373.txt>.
>
> Thanks,
> Tom
>
Attachment:
ipv6-icmp.cap
Description: Binary data