Hello,
I have attached to this email a short capture of a token ring frame
which is decoded as source routed but the frame is not source routed.
This must be a bug in interpreting the RII bit in the source address
field.
To be more convinced one could download the dualhome.cap.gz capture from
sample captures page of ethereal and filter on "tr.rif" and see that it
does not find any frame with rifs but there are for sure some frames
with rif.
I tried to look into the "packet-tr.c" file to find the bug, but instead
of finding the bug I found that token ring dissector tries to correct
some bugs from linux kernels 2.0.x and from other strange OS-es.
Maybe would be a better idea to split the file in two separate files:
one for the old linux kernel 2.0.x with all the possible bugs in it, and
one clean packet-tr.c file for newer kernels and other platforms.
And the selection between the two files would be at compile time, if the
kernel is 2.0.x then include the work-around file,if not then include
the plain file.
ÔòĄ @ ńę9ź 4 4 @Ŕ ZČÜBB Z ; Z ; 3 ńę9tÎ 4 4 @Ŕ ZČÜBB Z ; Z ; 3 ńę9ŕ 4 4 @Ŕ ZČÜBB Z ; Z ; 3
