3 ms·
Would there have been a better way to do design beacons? The general problem is a device needing to advertise itself for other devices to connect to, other de
by londons_explore 5y ago
Would there have been a better way to do design beacons? The general problem is a device needing to advertise itself for other devices to connect to, other devices which might not be capable of any faster rate...
Beacons being 350 bytes is pretty stupid though... They could have been 20 bytes long, saying "I'm a device with mac address XXX, plz contact me to know what services I have on offer".
- r1ch 5y agoIn retrospect, definitely. But a huge part of why Wi-Fi is so successful is the wide compatibility, so we're stuck with a design that is 20+ years old. Beacons also serve to do power saving wake-ups and various other things these days, and there's room to optimize them if the Wi-Fi alliance were stricter - some vendors are broadcasting their manufacturer and model (and sometimes serial number!) every 100ms as well as lots of other unnecessary information elements.
- tradertef 5y agoThere is out-of-band discovery for devices that support multiple bands. That should help in 6 GHz band but it looks more and more that 2.4 GHz will be only for discovery in the future.. https://www.extremenetworks.com/extreme-networks-blog/the-off-road-trail-to-6-ghz-ap-discovery/ https://www.extremenetworks.com/extreme-networks-blog/the-of...
- SavantIdiot 5y agoBeacons also have to broadcast the DTIM which allows stations to come out of standby if there is data waiting for them. This can be up to 128 bytes. But I agree, beacons are stupidly fat. The basic beacon is quite small except for the additional tags. If you fire up wireshark you'll see the bulk of the bytes in broadcasting all kinds of feature nonsense that IMHO should only be broadcast during a request to join. e.g the beacon frame is 24B on my Netgear, but the tagged paramters are 300 bytes. Sure, the SSID and DTIM are in there, but then there's a bunch of extended support rates, RSN info, HT info, and vendor specific stuff (Microsoft WMM/WME parameters, 3Com stuff... huh??)