Ethereal-dev: Re: [Ethereal-dev] dissector port clash (e.g. SNMP vs. TFTP)

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: Thomas Anders <thomas.anders@xxxxxxxxxxxxx>
Date: Tue, 11 May 2004 21:49:37 +0200
Martin Regner wrote:

One way of solving this particular problem could maybe be to add a
preference setting in SNMP
dissector that specifies if it should start up a conversation.


I had exactly the same idea, especially since most real-world SNMP
traffic (as in the sample capture) actually either goes to or from
one of the well-known ports (161,162), so the conversation code
just introduces problems instead of benefits. What I'm wondering
is if we should rather solve this individually per dissector or more
generally, given that a dozen dissectors seem to use similar code
here.

Thoughts?


+Thomas

--
Thomas Anders <thomas.anders at blue-cable.de>