MMTypes used in the demo and the MMTypes defined in the HPGP spec

[tropxy]

Hi,

I have been digging a bit into the slac code and HPGP spec and I noticed the following.

Whilst in the spec the MMType CM_MNBC_SOUND.IND is defined as 0x6078 (page 518 HPGP version 1.1 Feb, 2012), in
here

open-plc-utils/slac/evse_cm_mnbc_sound.c

Line 108 in bb50f63

else if (LE16TOH (homeplug->homeplug.MMTYPE) == (CM_MNBC_SOUND | MMTYPE_IND))

, it is expected:

CM_MNBC_SOUND | MMTYPE_IND

which is

0x6074 | 0x0002

which results in the hexadecimal value:
0x6076

And this is not the same as stated in HPGP spec.
Like this, the same happens with other MMTypes used by the Qualcomm demo. I suppose I am missing here something, but I dont know what. Can someone tell me what?

Thank you in advance!
André

[oliviermaridat]

Hello @tropxy

I can confirm a CM_MNBC_SOUND.IND is defined by 0x6076 (0x6074 | 0x0002).

And in HPGP 1.1.1 July 4, 2013, CM_MNBC_SOUND is defined as 0x6074 (in table 11-6, which means 0x6076 for MNBC_SOUND.IND).

Best regards

Olivier

[tropxy]

And another question. When I tried to replicate for example the CM_MNBC_SOUND.IND and sniffed the package in wireshark, wireshark recognizes it as a HPGP packet but doesnt recognise it as a CM_MNBC_SOUND message. The same does NOT happen with a CM_SET_KEY. Given that wireshark has dissectors for Homeplug, I would expect wireshark to recognise the payload. Do you experience the same behaviour ?

[oliviermaridat]

Hi André!

Since at least 2.6 Wireshark is able to decode most HPGP paquets.

[tropxy]

I may be doing something wrong. My wireshark recognizes a CM_SLAC_PARM but not a CM_MNBC_SOUND. I will test it again and see if I can find the error. thanks and apologies for the email issue.

[tropxy]

OK, my linux machine wireshark was outdated. On my Mac I had the most recent one, but not in Linux, so now I can see the CM_MNBC_SOUND ;)

[tropxy]

Could also anyone tell me if the Cipher Suit is to be used or not? According to ISO15118-3 it shall not be used, because the SECURITY_TYPE is 0x00 (as also suggested by HPGP spec), but according with Qualcomm slac, it is used:

open-plc-utils/slac/pev_cm_slac_param.c

Line 126 in bb50f63

if (LE16TOH (confirm->CipherSuite) != (uint16_t) (session->counter))

[oliviermaridat]

If you intend to apply HPGP for ISO 15118-3, then, best is to follow ISO 15118-3.
DIN 70121 and ISO 15118-3 are overriding some parts of HPGP. (and yes, sometimes it is confusing and almost buggy)

Good luck!

[tropxy]

Hi again, do you know what is the base MM code used for the APCM_SET_CCo message?

[tropxy]

Does anyone knows? Thank you!

[tropxy]

I would really appreciate if someone can provide me an answer, thanks!