ZoneMinder Forums

Posted: **Sun Nov 27, 2016 3:21 am**

Hi,

I just ordered this camera

-
HD POE 1080P Onvif Network IP Cam 2MP 3ARRAY Indoor IR Dome CCTV Security Camera Listed for charity
This POE IP Camera must work with 48V POE NVR or Switch
http://www.ebay.com/itm/191952131633?_t ... EBIDX%3AIT
-

And I'm trying to get it to work with zoneminder.

So first thing is powering it up and I don't have a POE injector so I'm already stuck !

Searching online I found this POE injector that does 48V

POE Module Injector Over Ethernet Router 4 LAN + Power port for IP Camera 48V
http://www.ebay.com/itm/POE-Module-Inje ... SwbsBXjGxy

Both the POE injector and the camera claim to support 802.3af
However they don't seem to agree on what pin the power should be sent ?!?

The POE injector claims that power pins are pin 4&5 for + and pin 7&8 for -
While the camera claims that power pins are pin 1&2 for + and pin 3&6 for -

Looking at the wikipedia page
https://en.wikipedia.org/wiki/Power_over_Ethernet

It seems that officially the 802.3af pinout for power is pin 4&5 for + and pin 7&8 for -

So I don't really get this is the camera saying it wants power on the normal data pin ? Could it be an error by the seller ? What happens if I miswire the power to this camera ? Is it going to fry ?

Anybody with POE experience please enlighten me !

Posted: **Mon Jan 16, 2017 12:41 pm**

I am currently trying to get a HAIWVISION camera to work (HD IPC).

I just plugged it in to a PoE injector and it works fine. Well at least it starts up. I have not been able to make it work with zoneminder.

I don´t think you need to worry about PoE wiring.

Posted: **Mon Feb 06, 2017 8:35 pm**

My Haiwvision PoE cam now works. Se my HAIWVISION AK47L7 post.

Posted: **Mon Feb 20, 2017 3:04 am**

Beware these cameras, or at least clones bearing their sticker - hard to tell when sourced from China. They are loaded with spyware. After getting mine to work (thanks to the Sourceforge-hosted ONVIF), I noticed it had date and time displayed (wrong timezone). I realized that it had to be pre-configured to go to an NTP server somewhere, so I was curious as to where else it was going. Using tcpdump I saw it was going far too many places... so I put it on a VLAN that has no connection to the internet. Don't trust trying to restrict on firewall DHCP alone - you should sandbox it. Here's what mine does (it's 192.168.45.134), and that's just 40 packets in 20 seconds:

Code: Select all

root@pomerium:/etc/shorewall# tcpdump -i any tcp or udp and 'src or dst' 192.168.45.134 -c 40
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes
18:24:39.229238 IP tcd.newmember-appreciation.us.http > 192.168.45.134.bacula-fd: Flags [R.], seq 0, ack 3628972726, win 0, length 0
18:24:39.274545 IP 192.168.45.134.55080 > 255.255.255.255.4001: UDP, length 128
18:24:40.274426 IP 192.168.45.134.36743 > 255.255.255.255.4001: UDP, length 128
18:24:41.274365 IP 192.168.45.134.41917 > 255.255.255.255.4001: UDP, length 128
18:24:42.274379 IP 192.168.45.134.44426 > 255.255.255.255.4001: UDP, length 128
18:24:43.274553 IP 192.168.45.134.33882 > 255.255.255.255.4001: UDP, length 128
18:24:44.274158 IP 192.168.45.134.48310 > 255.255.255.255.4001: UDP, length 128
18:24:44.306874 IP 192.168.45.134.35089 > tcd.newmember-appreciation.us.http: Flags [S], seq 1185338536, win 14600, options [mss 1460,sackOK,TS val 326681 ecr 0,nop,wscale 3], length 0
18:24:44.307101 IP tcd.newmember-appreciation.us.http > 192.168.45.134.35089: Flags [R.], seq 0, ack 1185338537, win 0, length 0
18:24:44.335105 IP 192.168.45.134.33902 > 47.88.86.102.http: Flags [S], seq 3506145577, win 14600, options [mss 1460,sackOK,TS val 326684 ecr 0,nop,wscale 3], length 0
18:24:44.335266 IP 47.88.86.102.http > 192.168.45.134.33902: Flags [R.], seq 0, ack 3506145578, win 0, length 0
18:24:45.274798 IP 192.168.45.134.37329 > 255.255.255.255.4001: UDP, length 128
18:24:46.274220 IP 192.168.45.134.36689 > 255.255.255.255.4001: UDP, length 128
18:24:47.274064 IP 192.168.45.134.39528 > 255.255.255.255.4001: UDP, length 128
18:24:48.274346 IP 192.168.45.134.56192 > 255.255.255.255.4001: UDP, length 128
18:24:49.267798 IP 192.168.45.134.bacula-fd > plus.yourscaninform.us.http: Flags [S], seq 2739649445, win 14600, options [mss 1460,sackOK,TS val 327177 ecr 0,nop,wscale 3], length 0
18:24:49.267984 IP plus.yourscaninform.us.http > 192.168.45.134.bacula-fd: Flags [R.], seq 0, ack 2739649446, win 0, length 0
18:24:49.276998 IP 192.168.45.134.60126 > 255.255.255.255.4001: UDP, length 128
18:24:50.274404 IP 192.168.45.134.50410 > 255.255.255.255.4001: UDP, length 128
18:24:51.274191 IP 192.168.45.134.46500 > 255.255.255.255.4001: UDP, length 128
18:24:52.274079 IP 192.168.45.134.48572 > 255.255.255.255.4001: UDP, length 128
18:24:53.274183 IP 192.168.45.134.37092 > 255.255.255.255.4001: UDP, length 128
18:24:54.274687 IP 192.168.45.134.54498 > 255.255.255.255.4001: UDP, length 128
18:24:54.305783 IP 192.168.45.134.48698 > tcd.newmember-appreciation.us.http: Flags [S], seq 1510946324, win 14600, options [mss 1460,sackOK,TS val 327681 ecr 0,nop,wscale 3], length 0
18:24:54.305949 IP tcd.newmember-appreciation.us.http > 192.168.45.134.48698: Flags [R.], seq 0, ack 1510946325, win 0, length 0
18:24:54.318207 IP 192.168.45.134.36550 > 47.88.86.102.http: Flags [S], seq 2144979416, win 14600, options [mss 1460,sackOK,TS val 327682 ecr 0,nop,wscale 3], length 0
18:24:54.318498 IP 47.88.86.102.http > 192.168.45.134.36550: Flags [R.], seq 0, ack 2144979417, win 0, length 0
18:24:55.274105 IP 192.168.45.134.57008 > 255.255.255.255.4001: UDP, length 128
18:24:56.274576 IP 192.168.45.134.55572 > 255.255.255.255.4001: UDP, length 128
18:24:57.274172 IP 192.168.45.134.57377 > 255.255.255.255.4001: UDP, length 128
18:24:58.274188 IP 192.168.45.134.49586 > 255.255.255.255.4001: UDP, length 128
18:24:59.274343 IP 192.168.45.134.54479 > 255.255.255.255.4001: UDP, length 128
18:24:59.285374 IP 192.168.45.134.bacula-fd > tcd.newmember-appreciation.us.http: Flags [S], seq 3942356100, win 14600, options [mss 1460,sackOK,TS val 328179 ecr 0,nop,wscale 3], length 0
18:24:59.285537 IP tcd.newmember-appreciation.us.http > 192.168.45.134.bacula-fd: Flags [R.], seq 0, ack 313383376, win 0, length 0
18:25:00.273831 IP 192.168.45.134.55195 > 255.255.255.255.4001: UDP, length 128
18:25:01.274166 IP 192.168.45.134.38896 > 255.255.255.255.4001: UDP, length 128
18:25:02.273958 IP 192.168.45.134.47832 > 255.255.255.255.4001: UDP, length 128
18:25:03.274430 IP 192.168.45.134.50447 > 255.255.255.255.4001: UDP, length 128
18:25:04.274128 IP 192.168.45.134.47633 > 255.255.255.255.4001: UDP, length 128
18:25:04.324046 IP 192.168.45.134.34454 > plus.yourscaninform.us.http: Flags [S], seq 3076320602, win 14600, options [mss 1460,sackOK,TS val 328683 ecr 0,nop,wscale 3], length 0
40 packets captured

Posted: **Tue Feb 21, 2017 3:43 pm**

It phones home? 47.88.86.102 is jovision.com the manufacturer of the firmware.

More worrying to me is that it is impossible to change the root password. passwd says "ok, it is changed" but after camera reboot i´the password is back to default. On the other hand, this seems to be the case for a lot of cheap cameras....

ZoneMinder Forums

POE Camera HAIWVISION onvif 2.0 support ?

POE Camera HAIWVISION onvif 2.0 support ?

Re: POE Camera HAIWVISION onvif 2.0 support ?

Re: POE Camera HAIWVISION onvif 2.0 support ?

Re: POE Camera HAIWVISION onvif 2.0 support ?

Re: POE Camera HAIWVISION onvif 2.0 support ?