Poll - what is the oldest level of 2.4Ghz Wifi currently in use

[Tech9]

This is what option I have on UniFi per SSID, but it clearly states for higher density deployments.

 

[sfx2000]

This is what option I have on UniFi per SSID, but it clearly states for higher density deployments.

View attachment 66450

Again - you're change 80211_MCAST, not 80211_BCAST - I've seen this very behavior on UNFI and others (it's a feature, right?? - most professional AP's (and course OpenWRT) - going legacy free is the default

Another thought here is the whole CellDensity thing, where we can limit association requests based on the minimum basic rate - that's fine, but again, if you don't disable legacy support in the driver - the beacon and management frames are still going at on 1Mbps, not 6, 12, whatever...

Ideally you want to ensure that the HR-DSSS mentioned below is disabled...

 

[Tech9]

Disabling Wi-Fi standard has to be based on some collective agreement. We as users can't do much. Most consumer routers around don't even have such settings, most users don't know what 802.11b is. Device manufacturers give priority to compatibility.

 

[sfx2000]

Disabling Wi-Fi standard has to be based on some collective agreement. We as users can't do much. Most consumer routers around don't even have such settings, most users don't know what 802.11b is. Device manufacturers give priority to compatibility.

Consensus in WIfi-Alliance, IEEE 802.11 WG, and the Broadband Forum have all agreed to deprecate 802.11 legacy support for both wireless connectivity along with auth/encryption - e.g. let us remove 801.11b legacy rates - as OFDM rates have a much higher level of access - and getting rid of another WPA and lower...

And then we have the whole multicast to unicast thing - it's likely good, but it breaks the spec as this is not allowed at the network level - and there's some handwaving that say's we can get away with it.

We are at a point where the new normal is as follows

1) WPA2 or newer
2) 802.11g/a/n or newer
3) Multicast Allowed on WiFi - and let the router handle IGMP snooping/proxy

Anyways - I'm still in the industry, and this is where things are headed...

 

[user114514]

Again - you're change 80211_MCAST, not 80211_BCAST - I've seen this very behavior on UNFI and others (it's a feature, right?? - most professional AP's (and course OpenWRT) - going legacy free is the default

Another thought here is the whole CellDensity thing, where we can limit association requests based on the minimum basic rate - that's fine, but again, if you don't disable legacy support in the driver - the beacon and management frames are still going at on 1Mbps, not 6, 12, whatever...

Ideally you want to ensure that the HR-DSSS mentioned below is disabled...

View attachment 66452

Not sure about the original OpenWRT, but at least on QSDK, mgmt, mcast, bcast, rtscts can all be adjusted independently of the basic rate, of course this only changes TX, RX is still determined by the STA. This fact is useful, on 5GHz, I set the AP's mgmt to 54Mbps, and the STA with lower txpower will still send at a more reliable 24Mbps.

 

[user114514]

Consensus in WIfi-Alliance, IEEE 802.11 WG, and the Broadband Forum have all agreed to deprecate 802.11 legacy support for both wireless connectivity along with auth/encryption - e.g. let us remove 801.11b legacy rates - as OFDM rates have a much higher level of access - and getting rid of another WPA and lower...

We are at a point where the new normal is as follows

1) WPA2 or newer
2) 802.11g/a/n or newer
3) Multicast Allowed on WiFi - and let the router handle IGMP snooping/proxy

Anyways - I'm still in the industry, and this is where things are headed...

I highly doubt these powerless organizations can actually change this. The fact that everyone is ignoring the WiFi7 security requirements shows that these "enforced" specifications just don't work.

And then we have the whole multicast to unicast thing - it's likely good, but it breaks the spec as this is not allowed at the network level - and there's some handwaving that say's we can get away with it.

I think 802.11v DMS allows for multicast to unicast, but few products seem to actually advertise it.

 

[sfx2000]

I highly doubt these powerless organizations can actually change this. The fact that everyone is ignoring the WiFi7 security requirements shows that these "enforced" specifications just don't work.

Key point though - with Carrier Gateways - it does have impact, and at present, they're doing a better job about it...

I think 802.11v DMS allows for multicast to unicast, but few products seem to actually advertise it.

Meh - most folks never implemented 11v as it was generally unworkable...

Most vendors have gone up a layer using IGMP snooping at the NIC interface...

 

[sfx2000]

Not sure about the original OpenWRT, but at least on QSDK, mgmt, mcast, bcast, rtscts can all be adjusted independently of the basic rate, of course this only changes TX, RX is still determined by the STA. This fact is useful, on 5GHz, I set the AP's mgmt to 54Mbps, and the STA with lower txpower will still send at a more reliable 24Mbps.

They can be adjusted - that's openwrt, not QSDK or the MediaTek SDK - both of which are built on OpenWRT...

You can play with things - but remember, there are rules to be followed - play around, and suddenly find out your IP cameras seem to have problems staying connected...

 

[sfx2000]

I highly doubt these powerless organizations can actually change this. The fact that everyone is ignoring the WiFi7 security requirements shows that these "enforced" specifications just don't work.

Good thing that you're not in charge, eh?

This is likely a good situation for a FOFA response for the vendors - frack around and find out what does not work...

 

[user114514]

Good thing that you're not in charge, eh?

This is likely a good situation for a FOFA response for the vendors - frack around and find out what does not work...

I mean, unlike Bluetooth's "mandatory" certification and strict scrutiny, WFA certification is optional and tacitly allows cheating.
Qualcomm and MediaTek know exactly why OEMs choose to cheat, otherwise there wouldn't be some workarounds in the drivers to do so.

Key point though - with Carrier Gateways - it does have impact, and at present, they're doing a better job about it...

ISPs clearly have their own ecosystems. 802.11s and easymesh have been popularised on a variety of ISP variant models since they were introduced, but they have never appeared on any general models. mesh and reduced customer support frequency is clearly one of the bottom lines for OEMs, and ISPs can change this within their own ecosystems, but again have no influence outside of that.

Meh - most folks never implemented 11v as it was generally unworkable...

Most vendors have gone up a layer using IGMP snooping at the NIC interface...

This again shows that WFA and 802.11 are just a dead letter.