Ethereal-dev: [Ethereal-dev] weird colorization desegmentation interaction

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: aferen@xxxxxxxxxxxx (Andrew C. Feren)
Date: 18 Apr 2002 10:34:57 -0400
One of my local users discovered a weird bug.  If a user saves their
colorization preferences and restarts ethereal (or reloads the
tracefile) desegmentation stops working correctly.  (More specifically
all desegmentation stops.  The display looks as if desegmentation were
disabled.)

Even weirder is the fact that desegmentation breaks even if colorizing
something that has nothing to do with the flow being desegmented.  For
example a colorization filter of "arp" breaks desegmentation.  As arp
isn't even IP (never mind TCP) this is clearly not part of the flow to
be desegmented.

Where can I find some traces that will exercise desegmentation in one
or more protocols supported by the Ethereal distribution?  I'd like to
verify that what I am observing happens with other protocols than
mine.  (Maybe I'm doing something foolish in my dissector code.)

Any suggestions on where I might look for this bad interaction?  I'm
not sure where to begin my bug hunt.

-- 
-Andrew Feren
 Cetacean Networks, Inc.
 Portsmouth, NH