Hmm, you could try making the stream URLs yourself like rtsp://username:[email protected]:port/some/endpoint. There's a list of endpoints in the code. Then using something like VLC Media Player to attempt to connect to it. If that does not work then maybe they brought out a patch to fix this vulnerability 🤔

Haha unfortunately that's just how the camera picks it up, infrared stuff I'm guessing! Its red in real life :(

@@WillRosen dashed a life goal 😆

Whoops, good catch!

I'm not sure of the exact details of NTP, but you should be able to set the camera's time by hosting an NTP server on the same network which responds with the correct time. There's a link to the code I used in the description but I believe it's in Python 2

@@WillRosen thanks, I noted that, but within several hours looking from internet finally found yours video and started to find real progress I needeed some sleep and had nj motivation any more. I should study some more accurate mathematics, it has been over twenty years since last study (if mac address has 3 pcs of zeros in rowa, it is not 4 pcs of zeros in row :D ) I got stream visible in firefox and tested some general agent application for windows. I perhaps would use wifi if it could get configured to carera. Some way there must be, because it could get done via windows or y-cam app.

Awesome! But unfortunately I didn't capture anything to do with changing the camera settings. There is the http web server on port 80 but that only had the option to update stuff, I didn't progress past that login screen so I don't know what's beyond that

@@WillRosen That was also only thing I succeedeed to find. I tried to find some firmware (mine is from year 2014) from internet, but without results. Maybe somebody will do tasmota or esp or something else hack for these well packed cameras somehow sorewhere sometimes :)

Woohoo! That's awesome, shame about the last camera though 😕 if it's a newer model maybe they realised their old passwords were bad haha

@WillRosen I had a look at the firmware update login and see its still basic authorisation. My guess is that they changed the characters at each end. Maybe just one. I haven't pursued it any further. I did try to see what it did to stream but its all hidden by encryption it seems. Port 554 is open. I did do a firmware update years ago and it was a similar looking password from memory which I had to copy and paste. If only I had saved that !!!

I found four pins on the camera's circuit board that turned out to be UART. Opening a UART connection, I found my camera prints out the password in plain text during boot 😅 but then again I found this post where the UART connection requires a username and password so it's not a 100% reliable way to find it forums.zoneminder.com/viewtopic.php?t=14623

Hmm, if the script isn't finding any cameras the SOCKET_TIMEOUT may be too low, right now it only allows 0.01 seconds to connect because it has to check 255 addresses and I was getting bored waiting 😅 You can try increasing this or changing the script to use just use the camera's ip if you know it. This link is the only information I stumbled across relating to the vulnerability being fixed: team-sik.org/sik-2016-045/ It says it was fixed in 2016 but whether this means existing cameras were patched or only new cameras had the fix I don't know. Mine were never updated to my knowledge

Those get imported into Mixer as different texture sets and can complicate things. Generally, you want to avoid using more than one material on a mesh in Unity, as well, as it increases Draw Calls which have a significant impact on performance. You also do not need to do this material stuff, just use the texture paint mode and use "face selection masking" and the fill tool. It's faster and less work and results in one image file without baking or dealing with 40 materials.