Ethereal-dev: [Ethereal-dev] Possible etherreal bug

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: "Sapariya Manish" <icmani@xxxxxxxxxxxxxxxxxxxx>
Date: Mon, 14 Jan 2002 18:37:25 +0900
Hi everyone,
I dont know whether this is the correct place to report/discuss a bug,
but I couldnt find any other place where I can discuss this thing.

I am working on BGP4 and have one capture file which I think ethereal
is not interpreting properly.

In the attatched capture file (Packet no. 340) the AS Path for the *Second*
BGP update
is incorrectly interpreted. When the AS Path info is more than 256 bytes the
length
field uses two bytes and sets the flag to denote a "Extended Length"
attribute. However
when Ethereal is not interpreting this "Extended Length" AS path attribute.
It successfully
does the same for MP_REACH_NLRI attribute however.

The first Bgp update in the same packet shows all the information correctly.
Comparing
this both the update we can very well verify that both the updates are
formed properly.

If I am not in the right place could anyone please tell me where to discuss
this problem.

thanks,
manish

Attachment: ASPathChivadaWhen200AS
Description: Binary data