Ethereal-users: [Ethereal-users] RE: "Malformed" ASF RMCP ACK packets

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: "Rob Swindell" <swindell@xxxxxxxxxxxx>
Date: Tue, 22 Feb 2005 16:22:39 -0800
Re-sending due to lack of acknowledgement/response:

Ethereal (v0.10.4) is reporting received ASF RMCP ACK packets as being "malformed" when they appear to be perfectly valid. Example:

0000  00 0f 1f d7 cd 46 00 b0  d0 21 00 48 08 00 45 00   
0010  00 20 3d 9a 00 00 20 11  fd 44 ac 10 01 ef ac 10   
0020  05 df 02 6f 02 6e 00 0c  93 84 06 00 01 86 00 00   
0030  00 00 00 00 00 00 00 00  00 00 00 00               

This is an ASF RMCP ACK of an ASF RMCP Capabilities Request packet.

I can only guess that Ethereal is assuming that ASF RMCP ACK packets are supposed to include a data block, when in fact they do not
(see section 3.2.2.1 Note 1 in the ASF Specification).

Perhaps someone on the Ethereal development team can point out exactly what it is that Ethereal is expecting, but not finding, in
this packet?

Thanks,

Rob Swindell
Senior Staff Software Engineer
Broadcom Corporation
swindell@xxxxxxxxxxxx