<![CDATA[HLS GMAC fails after Invocation Counter reset]]>This is synthetic Gate 2 content. No meter identifier, authentication key, or customer data is present.

现场现象：Association LN 建立后，HLS GMAC challenge 返回成功，但下一次请求得到 OtherReason。The likely boundary is the Invocation Counter read/write sequence, not network reachability.

Field Synthetic value What it proves
Security suite 0 test vocabulary only
Client counter 42 request-side observation
Server counter 43 independent readback required

Long APDU fixture (intentionally unwrapped):

000102030405060708090A0B0C0D0E0F101112131415161718191A1B1C1D1E1F202122232425262728292A2B2C2D2E2F303132333435363738393A3B3C3D3E3F404142434445464748494A4B4C4D4E4F505152535455565758595A5B5C5D5E5F606162636465666768696A6B6C6D6E6F707172737475767778797A7B7C7D7E7F808182838485868788898A8B8C8D8E8F909192939495969798999A9B9C9D9E9FA0A1A2A3A4A5A6A7A8A9AAABACADAEAFB0B1B2B3B4B5B6B7B8B9BABBBCBDBEBF

Recommended proof order: capture AARQ/AARE, capture HLS action request/response, then read the counter again from a fresh association.

]]>https://dlms.sharur.org/topic/2/hls-gmac-fails-after-invocation-counter-resetRSS for NodeFri, 16 Oct 2026 19:48:55 GMTSat, 22 Aug 2026 06:18:39 GMT60<![CDATA[Reply to HLS GMAC fails after Invocation Counter reset on Sat, 22 Aug 2026 06:18:39 GMT]]>中文补充：高认证成功日志只能证明认证阶段完成，仍需把后续 GET/SET 的响应与同一连接、同一调用计数器关联起来。

]]>https://dlms.sharur.org/post/4https://dlms.sharur.org/post/4Sat, 22 Aug 2026 06:18:39 GMT<![CDATA[Reply to HLS GMAC fails after Invocation Counter reset on Sat, 22 Aug 2026 06:18:39 GMT]]>Counter readback from a fresh synthetic association was 43. This narrows the issue to stale client state; it does not prove any physical meter outcome.

]]>https://dlms.sharur.org/post/3https://dlms.sharur.org/post/3Sat, 22 Aug 2026 06:18:39 GMT