Purduephotog
Getting the hang of it
- Oct 30, 2016
- 204
- 77
I was going to be lazy and put some pogo-pins together.
Turns out (if I may suggest) that adding a switch/hub in-between the computer and the camera- and also running ping -t with the IP of the camera, did the trick.
Until that point I never got to see any traffic of it attempting to boot/tftp. But the minute (and I repeated it many times) I started running the ping test (after clearing the ARP table) the camera connected each and every time.
So.. maybe it was the POE switch. Maybe it was the ping. But it worked and I'm happy.
Unfortunately the nvr won't force its credentials down into the camera, which means I can't just swipe them and figure out how to log into the damn thing locally.
Sigh.
Also, Alastair good Sir, if you already have an environment sent for unpacking firmware- have you seen this one ?
https://s3.amazonaws.com/mfs.ezvizlife.com/CS-X4-104P&108P&116P_v3.4.90_180413.rar
(My current PIT..Rear End)
Turns out (if I may suggest) that adding a switch/hub in-between the computer and the camera- and also running ping -t with the IP of the camera, did the trick.
Until that point I never got to see any traffic of it attempting to boot/tftp. But the minute (and I repeated it many times) I started running the ping test (after clearing the ARP table) the camera connected each and every time.
So.. maybe it was the POE switch. Maybe it was the ping. But it worked and I'm happy.
Unfortunately the nvr won't force its credentials down into the camera, which means I can't just swipe them and figure out how to log into the damn thing locally.
Sigh.
Also, Alastair good Sir, if you already have an environment sent for unpacking firmware- have you seen this one ?
https://s3.amazonaws.com/mfs.ezvizlife.com/CS-X4-104P&108P&116P_v3.4.90_180413.rar
(My current PIT..Rear End)