Sorry, IPv7 is an internal code-name for using the 0x8000 bit
of the offset field. My point was that when that bit is set (=1)
it shows up as 0 in the display and as an 0x80 in the hex dump.
Ethereal does not generally get in the way of seeing what we
want to see. It is mostly a human-factors issue to show a 0 in
one display when the reality is a 1. The bit goes right past the
software of common stacks. So do the RIFRAF Routing bits,
and those are better interpreted over time. It is hard for a
static tool to show what is going on there. One has to ping the
remote stack to see what is returned to develop a fingerprint
or signature to classify a machine. The classification can then
be used in decisions about where the system fits in the routing
structure.
Jim Fleming
http://www.dot-biz.com/IPv4/Tutorial/
http://www.IPv8.info
IPv16....One Better !!
----- Original Message -----
From: "Guy Harris" <guy@xxxxxxxxxx>
To: "Jim Fleming" <jfleming@xxxxxxxx>
Cc: "Gilbert Ramirez" <gram@xxxxxxxxxxxxxxx>; "Guy Harris" <guy@xxxxxxxxxx>; "Michael Tuexen" <Michael.Tuexen@xxxxxxxxxxxxxxxxx>;
<ethereal-dev@xxxxxxxxxxxx>
Sent: Tuesday, December 18, 2001 3:34 PM
Subject: Re: [Ethereal-dev] Searching for packets with incorrect checksums
> > The IPv7 bit seems to be handled differently. When set, it shows
> > in the hex field as 0x80 but in the display as a 0x00.
>
> There's no IPv7 dissector in Ethereal, so if it's handled differently, I
> suggest you talk to whoever wrote it (and ask them whether anybody's
> done anything about IPv7 since 1993; all the stuff Google found about it
> seems to date back to 1992-1993).
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
