RMCP dissector doesn't support "Secure RMCP"
"Rob Swindell" <[email protected]>
| Newsgroups | gmane.network.ethereal.user |
|---|---|
| Message-ID | <E0ED85DAA364D3468F7BE5D38048A698CB5708@NT-IRVA-0751.brcm.ad.broadcom.com> |
Ethereal already correctly parses ASF RMCP traffic, but doesn't recognize "Secure RMCP" traffic (on UDP port 664), as defined in the ASF 2.0 specification. See the attached capture of a valid Secure RMCP "Open Session" request and response. Here's a link to the ASF specification which defines the format of non-secure RMCP (ASF 1.0) and Secure RMCP (ASF 2.0) packets: http://www.dmtf.org/standards/documents/ASF/DSP0136.pdf The difference between RMCP and Secure RMCP is that Secure RMCP traffic is received on a different UDP port and the RMCP message is encapsulated in an RSP header and trailer (defined in the ASF 2.0 specification reference above). Thanks in advance, Rob Swindell Senior Staff Software Engineer Broadcom Corporation 949-585-6493 [email protected] _______________________________________________ Ethereal-users mailing list [email protected] http://www.ethereal.com/mailman/listinfo/ethereal-users
Open Secure Session.cap
(application/octet-stream, 304 B) - not displayed