![key light elgato key light elgato](https://4frag.ru/image/cache/data/Stream/Aksessuary/elgato-key-light-air-5-1000x1000.jpg)
That allows the AP to derive a Pairwise Transient Key for the computer, and for the computer to derive a PTK for the AP. The next thing that happens, if you're using WPA2, is that a protocol called EAPOL (which stands for Extensible Authentication Protocol Over LAN, which doesn't really mean anything) is used to allow a four-way handshake to occur between the AP and the computer. Now the computer is "associated", but it's not yet able to talk on the network, because it hasn't done the right dance yet. It writes those information elements into a Probe Response, and sends it back to the computer. The AP then compares the things it supports, to the things the client supports, and comes up with a common set of features that both can support.
#Key light elgato mac
So the computer then writes a Probe Request frame based on those information elements, so it knows what kind of radio the AP has, and it puts in some information about itself (like what MAC address it uses, what kind of radio it has, what kinds of encryption it can support) and sends it to the AP.
![key light elgato key light elgato](https://hanoicomputercdn.com/media/lib/47552_ElgatoKeyLight12.jpg)
It reads the information elements in the beacon frame, which include things like what kinds of encryption it supports, what extended wifi features it supports, and what kind of radio the AP has. When your device- let's say it's a computer- wants to connect to a network, it tunes to a channel, listens for a few hundred milliseconds and gathers all the beacon frames it can hear on that channel. It contains the MAC address of the access point, its name (which is called an SSID, for some reason), and a set of what are called Information Elements. An access point sends a special frame every 102.4 milliseconds called a beacon. See, the way wifi actually, at a fundamental level, works is using special frames. The longer answer is: some devices have busted firmware that gets confused when they see extra stuff. The answer is: yes, mostly, it only applies to devices that work with it.
![key light elgato key light elgato](https://i.ytimg.com/vi/aGww_foP3FA/maxresdefault.jpg)
Maybe I'm trying to push the curve too hard? There's just some lingering weirdness, and it all seems to hinge on that WPA3 setting. So I made some really good progress there! I ended up redoing our entire network yesterday - matching up MAC addresses and renaming every device - rebooting each one to get it connect to the "nearby" eero - and getting us back up to good Google Fiber speeds on the eeros: 900+ up and down.
![key light elgato key light elgato](https://basic-tutorials.com/wp-content/uploads/2020/01/Key_Light_Air_Lifestyle_01-scaled.jpg)
#Key light elgato how to
I'm just wondering if I need to keep WPA3 off for now, until all the manufacturers and devices figure out how to work with it? But then, when I turn it back on, the Elgato drops. The Elgato pairing process doesn't even work at all when WPA3 is enabled, so I set it up with WPA3 off.The thing both these devices (Keylight and Skybell) have in common is that you use your phone to initially set them up by "sharing" your network credentials - connecting your phone to those devices, passing along the wi-fi network you want them to use, then reconnecting to your regular wi-fi instead of the device. It seems that when WPA3 is enabled, the Keylight drops off the network, and when I toggle WPA3 off, it comes back online. A couple things on the network got knocked off - our Skybell (which I re-paired) and my Elgato Keylight Air (via Control Center). When 3.19 arrived, I was excited to try out the WPA3 for all our Apple devices.