Is this an issue with decoding the 802.11be management frame ETH PHY Bits 64-71?

asked 2026-03-27 00:04:18 +0000

xtu
1

updated 2026-03-28 18:28:41 +0000

Guy Harris
19905 ●3 ●682 ●207

I am using Wireshark to capture the 802.11be management frame. (Not able to add figure.) In the Association Request frame, one of the bit fields in ETH PHY Capabilities Information is displayed as: ETH PHY Bits 64-71 0X111100. However, the 1111 is extra bits and not defined in the 802.11be spec. I check that it will change to 4444 in the Association Response frame from an AP. Please let me know if you face the same issue. Thank you!

edit retag flag offensive close merge delete

add a comment

answered 2026-03-28 20:18:17 +0000

Chuckc
3148 ●6 ●661 ●20

updated 2026-03-28 20:37:13 +0000

Is there a typo / auto-correct in your question?
Is the field wlan.eht.phy_capabilities.bits_64_71 EHT PHY Bits 64-71? (Wireshark dfef: wlan)
(EHT not ETH)

Fixed in 23352: ieee80211: update code to final 802.11be amendment .
(There is a bug fix bundled in with this merge that has not been cherry picked back to the 4.6 branch.)

    {&hf_ieee80211_eht_phy_bits_64_71,
     {"EHT PHY Bits 64-71", "wlan.eht.phy_capabilities.bits_64_71",
-     FT_UINT24, BASE_HEX, NULL, 0x0, NULL, HFILL }},
+     FT_UINT8, BASE_HEX, NULL, 0x0, NULL, HFILL }},

(See sample capture ieee80211_eht_ml_sta_profile.pcapng attached to 19425: ieee80211 elements filter in EHT Multi-link sta profile)

EHT PHY Capabilities Information
    EHT PHY Bits 0-15: 0x0008
    EHT PHY Bits 16-31: 0x0000
    EHT PHY Bits 32-39: 0x00
    EHT PHY Bits 40-63: 0x000c30
    EHT PHY Bits 64-71: 0x002200
        .... ...0 = Rx 1024-QAM In Wider Bandwidth DL OFDMA Support: Not supported
        .... ..0. = Rx 4096-QAM In Wider Bandwidth DL OFDMA SUpport: Not supported
        .... .0.. = 20 MHz-Only Limited Capabilities Support: Not supported
        .... 0... = 20 MHz-Only Triggered MU Beamforming Full BW Feedback And DL MU-MIMO: Not supported
        ...0 .... = 20 MHz-Only MRU Support: Not supported
        000. .... = Reserved: 0x0

edit flag offensive delete link

Comments

Correct output from 4.7.0rc0-2329-g1599134044dd:

EHT PHY Capabilities Information
    EHT PHY Bits 0-15: 0x0008
    EHT PHY Bits 16-31: 0x0000
    EHT PHY Bits 32-39: 0x00
    EHT PHY Bits 40-63: 0x000c30
    EHT PHY Bits 64-71: 0x00
        .... ...0 = Rx 1024-QAM In Wider Bandwidth DL OFDMA Support: Not supported
        .... ..0. = Rx 4096-QAM In Wider Bandwidth DL OFDMA Support: Not supported
        .... .0.. = 20 MHz-Only Limited Capabilities Support: Not supported
        .... 0... = 20 MHz-Only Triggered MU Beamforming Full BW Feedback And DL MU-MIMO: Not supported
        ...0 .... = 20 MHz-Only MRU Support: Not supported
        000. .... = Reserved: 0x0

Chuckc ( 2026-03-28 20:30:03 +0000 )edit

add a comment

Is this an issue with decoding the 802.11be management frame ETH PHY Bits 64-71?

1 Answer

Comments

Your Answer

Question Tools

Stats

Related questions

Is this an issue with decoding the 802.11be management frame ETH PHY Bits 64-71? edit

1 Answer

Comments

Your Answer

Question Tools

Stats

Related questions

Is this an issue with decoding the 802.11be management frame ETH PHY Bits 64-71?