Reverse-engineering the UniFi inform protocol
tamarack.cloud
Reverse-engineering the UniFi inform protocol
1–10 of 81 posts
Re: Reverse-engineering the UniFi inform protocol
#2> ("TNBU" is "UNBT" backwards, presumably UniFi Broadcast Technology.)
This seems like an odd misunderstanding, especially because the correct inversion “UBNT” is the default login name for most UniFi web UIs.
You might have a bit of dyslexia, OP!
Re: Reverse-engineering the UniFi inform protocol
#3> ("TNBU" is "UNBT" backwards, presumably UniFi Broadcast Technology.) This seems like an odd misunderstanding, especially because the correct inversion “UBNT” is the default login name for most UniFi web UIs. You might have a bit of dyslexia, OP!
ubnt has been the ubiquiti default login at least back to 2010 when I started using their products, before UniFi was a brand. I always assumed it was short for Ubiquiti Networks.
Re: Reverse-engineering the UniFi inform protocol
#4> ("TNBU" is "UNBT" backwards, presumably UniFi Broadcast Technology.) This seems like an odd misunderstanding, especially because the correct inversion “UBNT” is the default login name for most UniFi web UIs. You might have a bit of dyslexia, OP!
You might be onto something there! But yes, good catch, I'll get that updated.
Re: Reverse-engineering the UniFi inform protocol
#5> ("TNBU" is "UNBT" backwards, presumably UniFi Broadcast Technology.) This seems like an odd misunderstanding, especially because the correct inversion “UBNT” is the default login name for most UniFi web UIs. You might have a bit of dyslexia, OP!
ubnt has been the ubiquiti default login at least back to 2010 when I started using their products, before UniFi was a brand. I always assumed it was short for Ubiquiti Networks.
Sure, but the parent was saying this part was odd:
> "TNBU" is "UNBT" backwards
TNBU is clearly NOT uNbt backwards.
Re: Reverse-engineering the UniFi inform protocol
#6[deleted]
Re: Reverse-engineering the UniFi inform protocol
#7Earlier quoted context omitted.
ubnt has been the ubiquiti default login at least back to 2010 when I started using their products, before UniFi was a brand. I always assumed it was short for Ubiquiti Networks.
Sure, but the parent was saying this part was odd: > "TNBU" is "UNBT" backwards TNBU is clearly NOT uNbt backwards.
Using the network byte ordering (big endian) of UBNT as the magic number in the protocol is a nice touch.
Re: Reverse-engineering the UniFi inform protocol
#8Earlier quoted context omitted.
Sure, but the parent was saying this part was odd: > "TNBU" is "UNBT" backwards TNBU is clearly NOT uNbt backwards.
Using the network byte ordering (big endian) of UBNT as the magic number in the protocol is a nice touch.
I believe they used MIPS processors in their early gear, so that makes sense.
Re: Reverse-engineering the UniFi inform protocol
#9Is it just me that pretty much cannot read most of the text in the "Reading the MAC" code block? I don't know if it's because I use dark mode, but some of the text is #24292E on top of #141A16, which for me at least is practically invisible
Re: Reverse-engineering the UniFi inform protocol
#10Bit of a thread-jack, but has anyone reverse-engineered the UniFi camera adoption protocol? I was surprised to discover that, unlike the APs, the cameras can't be adopted through the Unifi Software Controller that you can just throw into a Docker container. You're supposed to do that through their NVR appliance (Unifi Protect). I was hoping to just use them with my open-source NVR. They seem to be about the only option for a reasonably priced, larger image sensor camera that is not made by a company participating in the Uyghur genocide (Hikvision, Dahua, Univision, Huawei).
I found https://community.home-assistant.io/t/unifi-cameras-without-... in which someone sshed in, edited some config files by hand, and got streaming to work for the current boot. One could probably take that a bit further and, you know, save the config to flash. But it'd be nice to just do it the way their controller does and know it's going to work for future firmware updates and such.
They also stream by connecting to your NVR with modified version of flv, rather than you connecting to them with RTSP, which is annoying but can be worked around.