Ethereal-users: RE: [Ethereal-users] problems with decode of ACF and infoRequestR esponse
Title: RE: [Ethereal-users] problems with decode of ACF and infoRequestResponse
Well,
When the protocol is listed as:
"Source port: 1717 Destination port: h323gatestatCS: empty RAS: infoRequestResponse",
I can't tell what type of H225 packet is is until I scroll to the end. Besides, no other H225 packet is displayed this way, so I don't think that it was intentional.
It's a cleaner output to just show the info collumn as "RAS: infoRequestResponse". and consistent with the other decodes.
It's just easier to look at with the shorter name, that's all.
Thanks for checking in the fix.
Mike Oliveras
-----Original Message-----
From: Guy Harris [mailto:guy@xxxxxxxxxxxx]
Sent: Monday, November 10, 2003 4:43 PM
To: martin.regner@xxxxxxxxx
Cc: ethereal-users@xxxxxxxxxxxx
Subject: Re: [Ethereal-users] problems with decode of ACF and
infoRequestResponse
On Nov 9, 2003, at 2:35 AM, martin.regner@xxxxxxxxx wrote:
> Yes there is a fault in decoding of EndPoint sequence. There should be
> a sequence of AliasAddress-es.
>
> I have made a patch that seems to solve that problem and also avoids
> that a pdu_item results in writing to the Info column.
Checked in.
Why is having a pdu_item update the Protocol or Info column a problem?
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users
