jeffreykog / unifi-inform-protocol Goto Github PK

Thank you for your work.
I think it would be great to mention that other devices (at least M series) using same protocol for the device discovery. At least valid for the M and AC access points/CPE. I am going to write a small tool to make discovery from Linux w/o using Java, etc.

When an unadopted UAP is connected to the network, it will start announcing itself on the layer 2 network. It will do this in 2 > ways:

As a broadcast packet (255.255.255.255)
As a multicast packet to 233.89.188.1

Layer 2 (Ethernet) does not have IP Addresses. Also, Ethernet does not distinguish between multicast and broadcast.
There is a range of reserved multicast MAC Addresses for specific purposes. And there is also the special mac address FF:FF:FF:FF:FF:FF. In every case, multicast ethernet frames are spammed to the whole collision domain (hubs) or to every port (switch) that is connected.

Additionally, you have to enable layer 2 adoption specifically in the controller. So I think L3 adoption is the default and does not neccesarily need additional configuration in the devices, prior to adopt them in L3

Actually the UDP communication that you found out on port 10001 would be, strictly speaking, already L4

Yes, it was used for snappy for a while, I have captures and a working decoder for flags = 5 ( encryption + snappy ). The compression seems to be depreciated and they are back to zlib and moved on to GCM.