Omada client identity
ok....wondering if anyone is interested in this docker container I'm building up to provide additional context and identity of devices on a network. It is limited now to a single subnet, due to using broadcast/multicast interception. Keen for feedback here...initial goal was to determine what is on the network and provide consistant naming of devices back into the Omada Controller.
It would be super handy if TP-Link updated their v6 API to allow updating all elements of clients on the network. I'd love to see TP-Link get a bit smarter about understanding clients on the network as there is a lot that can be done with DHCP fingerprinting, MDNS inspection etc.
u/farsonic — 2 days ago