@whoslooking - So what was that mtdx talk on another thread about? I was reading that thread and didn't get a clear picture if it's possibly the same issue.
@whoslooking - I also tried that 4line firmware. No luck and by the way. I'm a idiot. I found the camera boxes and it appears the broken one was made on 06/2015 and 5.3.0 150513. Yet it was loaded with 5.2.5 141201.
Here are my findings. I took a laptop, switch, broken camera and hooked them all up directly. This is by passing my normal poe switch. I took a 12v power supply and powered the camera that way. I addressed the laptop as 192.0.0.128/8 (255.0.0.0). Then ran wireshark and the tftp server. I found...
I went ahead and order the following.
http://www.ebay.com/itm/111593270026
http://www.ebay.com/itm/180953299346
http://www.ebay.com/itm/201429406150
Hopefully everything comes sometime mid next week. But overall thanks for the support guys. It looks like the bootloader maybe okay, so it...
I setup a port mirror on the switch last night and didn't see much coming out of the camera. So I'm going to bring a ethernet tap home from work and see if the issue persists. I'm sure that the bootloader is corrupt, just based on how it's acting. Anyone know a place selling a serial cable for...
OK. BTW, no go with that firmware. I don't even see a attempt for any frames to 192.0.0.128.
192 243.579199 192.0.0.128 -> 192.0.0.64 ICMP 74 Echo (ping) request id=0x0001, seq=1126/26116, ttl=128
193 248.579399 192.0.0.128 -> 192.0.0.64 ICMP 74 Echo (ping) request id=0x0001...
I was going to say that sucks. OK. I'll give that a spin. BTW, looking at my switches FDB. I noticed the switch learned two mac address. Not sure if anyone finds that interesting.
@alastairstevenson - I'll try this remotely from work today. I'm wondering if my switch is doing something crazy. Worst case I'm going to bring the Ethernet tap we have at work and watch the mirror port.
@whoslooking - I have other cameras (white box) that took the 5.3.0 upgrade without...
@whoslooking - I'll give it another try. It's just weird that it will boot up in its redboot like state. Then go away for about 5 minutes before appearing on SADP as 192.168.1.64. Running a nmap scan doesn't show much of any port listening. Just like others have expressed.