Ethereal-dev: Re: [Ethereal-dev] H323 Analysis cleanup

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@xxxxxxxxx>
Date: Fri, 01 Oct 2004 02:45:51 -0700
Francisco Alcoba (ML/EEM) wrote:


The code adds H323 conversations over UDP to the conversation list,
but it does not analyze them or sets them as filter because it later
assumes the transport is TCP.   I have added a parameter to remember the
transport and build the filters accordingly.


Checked in.


3) Does someone know what would happen if the H225 packet is encapsulated
-e.g. in GRE-?
Presumably you mean the IP datagram(s) that ultimately contain the H.225 packet is encapsulated inside GRE, or inside some protocol encapsulated inside GRE. If so... 


Would the code receive the addresses, ports, protocol of the encapsulating
or the encapsulated packet?
...then the code would get the information about the encapsulated packet - the IP dissector, when it's dissecting a GRE-encapsulated packet, overwrites the information put there by the IP dissector when it was dissecting the packet in which the GRE packet was encapsulated.