What's new

Linksys MR9600 - Maximum mesh nodes

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

chadster766

Very Senior Member
Can anyone advise me as to the maximum number of nodes that can be on this MESH network according to the info below?

Linksys MR9600 Beacon Frame (Primary Velop Node) (HE Capabilities)

Code:
Ext Tag: HE Capabilities (IEEE Std 802.11ax/D2.0)
    Ext Tag Number: HE Capabilities (IEEE Std 802.11ax/D2.0) (35)
    Ext Tag length: 35
    HE MAC Capabilities Information: 0x001208000d
        .... .... .... .... .... .... .... .... .... ...1 = +HTC HE Support: Supported
        .... .... .... .... .... .... .... .... .... ..0. = TWT Requester Support: Not supported
        .... .... .... .... .... .... .... .... .... .1.. = TWT Responder Support: Supported
        .... .... .... .... .... .... .... .... ...0 1... = Fragmentation Support: Support for dynamic fragments in MPDUs or S-MPDUs (1)
        .... .... .... .... .... .... .... .... 000. .... = Maximum Number of Fragmented MSDUs: 0
        .... .... .... .... .... .... .... ..00 .... .... = Minimum Fragment Size: No restriction on minimum payload size (0)
        .... .... .... .... .... .... .... 00.. .... .... = Trigger Frame MAC Padding Duration: 0
        .... .... .... .... .... .... .000 .... .... .... = Multi-TID Aggregation Support: 0
        .... .... .... .... .... ...0 0... .... .... .... = HE Link Adaptation Support: No feedback if the STA does not provide HE MFB (0)
        .... .... .... .... .... ..0. .... .... .... .... = All Ack Support: Not supported
        .... .... .... .... .... .0.. .... .... .... .... = UMRS Support: Not supported
        .... .... .... .... .... 1... .... .... .... .... = BSR Support: Supported
        .... .... .... .... ...0 .... .... .... .... .... = Broadcast TWT Support: Not supported
        .... .... .... .... ..0. .... .... .... .... .... = 32-bit BA Bitmap Support: Not supported
        .... .... .... .... .0.. .... .... .... .... .... = MU Cascading Support: Not supported
        .... .... .... .... 0... .... .... .... .... .... = Ack-Enabled Aggregation Support: Not supported
        .... .... .... ...0 .... .... .... .... .... .... = Group Addressed Multi-STA BlockAck in DL MU Support: Not supported
        .... .... .... ..1. .... .... .... .... .... .... = OM Control Support: Supported
        .... .... .... .0.. .... .... .... .... .... .... = OFDMA RA Support: Not supported
        .... .... ...1 0... .... .... .... .... .... .... = Maximum A-MPDU Length Exponent: 2
        .... .... ..0. .... .... .... .... .... .... .... = A-MSDU Fragmentation Support: Not supported
        .... .... .0.. .... .... .... .... .... .... .... = Flexible TWT Schedule Support: Not supported
        .... .... 0... .... .... .... .... .... .... .... = Rx Control Frame to MultiBSS: Not supported
        .... ...0 .... .... .... .... .... .... .... .... = BSRP BQRP A-MPDU Aggregation: Not supported
        .... ..0. .... .... .... .... .... .... .... .... = QTP Support: Not supported
        .... .0.. .... .... .... .... .... .... .... .... = BQR Support: Not supported
        .... 0... .... .... .... .... .... .... .... .... = SR Responder Role: Not supported
        ...0 .... .... .... .... .... .... .... .... .... = NDP Feedback Report Support: Not supported
        ..0. .... .... .... .... .... .... .... .... .... = OPS Support: Not supported
        .0.. .... .... .... .... .... .... .... .... .... = A-MSDU in A-MPDU Support: Not supported
        0... .... .... .... .... .... .... .... .... .... = Reserved: 0x0
    HE Phy Capabilities Information
        .... ...0 = Dual Band Support: 0x0
            .... ...0 = Dual Band Support: Not supported
        0001 000. = Channel Width Set: 0x08
            .... ..0. = 40MHz in 2.4GHz band: Not supported
            .... .0.. = 40 & 80MHz in the 5GHz band: Not supported
            .... 0... = 160MHz in the 5GHz band: Not supported
            ...1 .... = 160/80+80MHz in the 5GHz band: Supported
            ..0. .... = 242 tone RUs in the 2.4GHz band: Not supported
            .0.. .... = 242 tone RUs in the 5GHz band: Not supported
            0... .... = Reserved: 0x0
        Bits 8 to 23: 0x200c
            .... .... .... 1100 = Punctured Preamble RX: 0xc
            .... .... ...0 .... = Device Class: 0x0
            .... .... ..0. .... = LDPC Coding In Payload: Not supported
            .... .... .0.. .... = HE SU PPDU With 1x HE-LTF and 0.8us GI: Not supported
            .... ...0 0... .... = Midamble Rx Max NSTS: 0x0
            .... ..0. .... .... = NDP With 4x HE-LTF and 3.2us GI: Not supported
            .... .0.. .... .... = STBC Tx <= 80 MHz: Not supported
            .... 0... .... .... = STBC Rx <= 80 MHz: Not supported
            ...0 .... .... .... = Doppler Tx: Not supported
            ..1. .... .... .... = Doppler Rx: Supported
            .0.. .... .... .... = Full Bandwidth UL MU-MIMO: Not supported
            0... .... .... .... = Partial Bandwidth UL MU-MIMO: Not supported
        Bits 24 to 39: 0xc002
            .... .... .... ..10 = DCM Max Constellation Tx: 0x2
            .... .... .... .0.. = DCM Max NSS Tx: 0x0
            .... .... ...0 0... = DCM Max Constellation Rx: 0x0
            .... .... ..0. .... = DCM Max NSS Rx: 0x0
            .... .... .0.. .... = Rx HE MU PPDU from Non-AP STA: Not supported
            .... .... 0... .... = SU Beamformer: Not supported
            .... ...0 .... .... = SU Beamformee: Not supported
            .... ..0. .... .... = MU Beamformer: Not supported
            ...0 00.. .... .... = Beamformee STS <= 80 MHz: 0x0
            110. .... .... .... = Beamformee STS > 80 MHz: 0x6
        Bits 40 to 55: 0x5b6f
            .... .... .... .111 = Number Of Sounding Dimensions <= 80 MHz: 7
            .... .... ..10 1... = Number Of Sounding Dimensions > 80 MHz: 5
            .... .... .1.. .... = Ng = 16 SU Feedback: Supported
            .... .... 0... .... = Ng = 16 MU Feedback: Not supported
            .... ...1 .... .... = Codebook Size SU Feedback: Supported
            .... ..1. .... .... = Codebook Size MU Feedback: Supported
            .... .0.. .... .... = Triggered SU Beamforming Feedback: Not supported
            .... 1... .... .... = Triggered MU Beamforming Feedback: Supported
            ...1 .... .... .... = Triggered CQI Feedback: Supported
            ..0. .... .... .... = Partial Bandwidth Extended Range: Not supported
            .1.. .... .... .... = Partial Bandwidth DL MU-MIMO: Supported
            0... .... .... .... = PPE Threshold Present: False
        Bits 56 to 71: 0x1883
            .... .... .... ...1 = SRP-based SR Support: Supported
            .... .... .... ..1. = Power Boost Factor ar Support: Supported
            .... .... .... .0.. = HE SU PPDU & HE MU PPDU w 4x HE-LTF & 0.8us GI: Not supported
            .... .... ..00 0... = Max Nc: Not supported
            .... .... .0.. .... = STBC Tx > 80 MHz: Not supported
            .... .... 1... .... = STBC Rx > 80 MHz: Supported
            .... ...0 .... .... = HE ER SU PPDU W 4x HE-LTF & 0.8us GI: Not supported
            .... ..0. .... .... = 20 MHz In 40 MHz HE PPDU In 2.4GHz Band: Not supported
            .... .0.. .... .... = 20 MHz In 160/80+80 MHz HE PPDU: Not supported
            .... 1... .... .... = 80 MHz In 160/80+80 MHz HE PPDU: Supported
            ...1 .... .... .... = HE ER SU PPDU W 1x HE-LTF & 0.8us GI: Supported
            ..0. .... .... .... = Midamble Rx 2x & 1x HE-LTF: Not supported
            00.. .... .... .... = Reserved: 0x0
 
HE beacon information doesn't contain that information.
 
I can't find any maximum node spec for what is listed in the beacon frame IEEE Std 802.11ax/D2.0.

Do you know what it is?
 
Number of mesh nodes is not an 802.11 parameter as far as I know.

Maybe you are referring to the maximum # of AIDs? That has nothing to do with mesh.

There is no beacon parameter that tells you the maximum # of RUs or AIDs that are supported. HE-MU trigger and other frame types associated with OFDMA will tell you how many AIDs are included in an OFDMA transmit frame. But that doesn't necessarily tell you the maximum supported.

AFAIK, none of the AX consumer routers on the market support more than 8 AIDs. More often the maximum is 4. This is per band.
 
I haven't seen these 802.11 AID limits with the Linksys Mesh. Many users have 8 or more nodes.
 
I haven't seen these 802.11 AID limits with the Linksys Mesh. Many users have 8 or more nodes.
Again, AIDs have nothing to do with mesh nodes. They determine the # of OFDMA STAs in a transmit frame.

Mesh does not use OFDMA.
 
Again, AIDs have nothing to do with mesh nodes. They determine the # of OFDMA STAs in a transmit frame.

Mesh does not use OFDMA.
Isn't AID more of a 802.11 wireless frame spec which all 802.11 protocols follow?

If this is the case then the maximum number of nodes is a unsigned int16 max value.
 
Last edited:
Isn't AID more of a 802.11 wireless frame spec which all 802.11 protocols follow?

If this is the case then the maximum number of nodes is a unsigned int16 max value.
Yes, AID (Association ID) is a general 802.11 term. I'm referring to AID12, which is specific to HE frames.

Please cite your reference that describes where the maximum number of mesh nodes is contained in an 802.11 frame. Even better would be the Wireshark filter. I have plenty of captures that I can look for it in.

At any rate, I don't think the information would be found in the HE part of the frame, since mesh or ESS is more basic.

Anyone more knowledgeable is welcome to jump in.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top