Exactly.
You need to start capture process before CMIP will initiate connection
procedure.
In this case ethereal will recognize following data pdus as CMIP data pdus.
ronnie sahlberg wrote:
During the signalling phase, you will have ACSE ontop of Presentation
and then CMIP ontop of ACSE.
During the normal command/data phase you will have CMIP directly ontop
of Presentation, but this only works IFF ethereal has already seen the
ACSE signalling packets that associate the cmip protocol/oid with the
current context id.
Do you have any example capture files you can send to me to test with?
the cmip dissector works somewhat but is still incomplete, mainly
due to lack of capture files to test with. There are also some bugs in
it i plan to address in the next few days/week.
On 6/22/05, Murray Ivan-qcor189 <Ivan.Murray@xxxxxxxxxxxx> wrote:
I cannot seem to decode messages on a CMIP interface that I am testing. I
believe I am getting the following instead:
8073 COTP Connection-Oriented Transport Protocol
8327-1 OSI Session Protocol
8327-1 OSI Session Protocol
8823 OSI Presentation Protocol
I am not enven sure if this is the CMIP message I should be expecting. CMIP
sits on TCP/IP, so I am not sure that this is even one of the messages. Any
help appreciated here. Has anyone every seen decoded CMIP messages? What
should it look like?
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users
