https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4447
--- Comment #2 from Guy Harris <guy@xxxxxxxxxxxx> 2010-02-01 21:10:15 PST ---
Yes, the discussion is probably best done on the dev list.
Note, though, that there are other capture formats that don't provide a traffic
type for ATM cells/AAL5 PDUs; the routines in wiretap/atm.c are used to try to
infer the traffic type from the VPI/VCI and the data in the PDU.
We're using preferences for a number of items that should be per-conversation
settings, along with a much broader definition of "conversation" that would
include connections both above and below the transport layer, including ATM
virtual circuits. Such a mechanism is probably what's called for here if the
heuristics from wiretap/atm.c are insufficient, so you can mark particular ATM
VCs as having a particular traffic type. (This also involves a generalization
of the "Decode as..." mechanism.) But, again, that's probably something where
the discussion should start on wireshark-dev.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
