Wireshark Version 2.6.10 (Git v2.6.10 packaged as 2.6.10-1~ubuntu16.04.0) shows: (same problem in Wireshark Version 3.0.6)
HomePlug AV protocol
MAC Management Header
.... ...1 = Version: 1.1 (1)
Type: Tone Map Rx Characteristics Confirmation (0xa091)
Fragmentation Info: 0x2019
Vendor MME
Tone Map Rx Characteristics Confirmation
Status: Success (0x00)
Reserved
Length: 3268
MME Subversion: 0
Reserved
Peer address: xxx (xxx)
Slot: 0
.... 0010 = Coupling: Unknown (2)
Number of Tone Maps in use: 6
Reserved
Tone map number of active carriers: 2690
Reserved
Guard Interval Length (GIL): 0
Reserved
Automatic Gain Control (AGC): 14
Reserved
Tone Map carriers (Total #ModulatedBits=19058 bit, Active #Carriers=2390, Average #Bits/Carrier=7,97 bit), Average SNR/Carrier=22,56 dB)
Slot 0 (in 1 byte) looks good.
HomePlug AV protocol
MAC Management Header
.... ...1 = Version: 1.1 (1)
Type: Tone Map Rx Characteristics Request (0xa090)
Fragmentation Info: 0x0000
Vendor MME
Tone Map Rx Characteristics Request
Reserved
Peer address: xxx (xxx)
Tone Map slot: 0
.... 0000 = Coupling: Primary (0)
Request is slot 0 (in 1 byte)
HomePlug AV protocol
MAC Management Header
.... ...1 = Version: 1.1 (1)
Type: Tone Map Tx Characteristics Confirmation (0xa071)
Fragmentation Info: 0x2018
Vendor MME
Tone Map Tx Characteristics Confirmation
Status: Success (0x00)
Length: 3264
Reserved
Peer address: xxx (xxx)
Slot: 512
Number of Tone Maps in use: 1542
Tone map number of active carriers: 2690
Reserved
Tone Map carriers (Total #ModulatedBits=20250 bit, Active #Carriers=2414, Average #Bits/Carrier=8,39 bit), Average SNR/Carrier=23,75 dB)
Confirmation is Slot 512 (in 2 bytes)
Is it a bug?
Where is the specification for
Tone Map Tx Characteristics Confirmation (0xa071)
Tone Map Rx Characteristics Request (0xa090)
Tone Map Rx Characteristics Confirmation (0xa091)
