Hello all, I know there has to be a plugin available that is being worked on
or in some company's private collection for 3GPP2 A10/A11 RP Interface
decoding. Anyway, since I could not find any public information relating to
the work or release of this decoding plugin for Ethereal, I have decided to
fill in this gap. A question that I have regarding this, is that there are
3GPP2 Vendor Specific Attributes, and I would like to know if these
attributes can be updated into the packet-radius.c source and somehow called
from the future packet-3grp.c in the works. Correct me if I am wrong, but it
appears the Ethereal dissector relies on the port number to make it's
decoding choices. If this is the case, is there a way for my decode routines
to call the Radius decode routines to do 3GPP2 Vendor Specific Attributes of
the packet, then come back to finish the 3GPP2 routines. Otherwise I will
have to add all of the functionality for Radius decoding directly to the
3GPP2 routines. Thanks.