Ethereal-dev: Re: [ethereal-dev] conversation wildcard entry

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: Guy Harris <gharris@xxxxxxxxxxxx>
Date: Sat, 21 Oct 2000 02:59:12 -0700
On Fri, Oct 20, 2000 at 11:01:44PM -0700, Guy Harris wrote:
> Checked in.

I redid the way wildcards are handled - you have to try wildcarding both
the source *and* destination port and/or both the source *and*
destination address passed to "find_conversation()", because the packet
for which you're trying to find the conversation may be going in the
opposite direction to the packet for which the conversation was
originally created.

(I also created different hash tables for wildcarded conversations, to
reduce the number of "is this a wildcard?" tests done when doing hash
lookups.)

This is sufficient to allow the TFTP dissector to use conversations
rather than being special-cased in the UDP dissector, and may also be
sufficient to handle a similar problem with SMTP (request goes from
client IP X port Y to server IP Z's well-known port, reply comes back
from some other port on server Z to client IP X port Y), but further use
may reveal other changes that should be made.