I mean when it's plugged into the NVR PoE ports with plug-and-play settings. Read the start of this thread.
Email alerts not working when Hikvision cameras connected to DS-7608NI-E2/8P
- Thread starter butwhy
- Start date
Del Boy,
In my cameras, isn't at "plug and play",
The first time I connect them it's already was with manual settings.
About the NVR upgrade, it's works, thansk .
Regards.
In my cameras, isn't at "plug and play",
The first time I connect them it's already was with manual settings.
About the NVR upgrade, it's works, thansk .
Regards.
@aster1x @alastairstevenson guys not to beat a dead horse to death but I am still unable to get camera to see the wan. just wanted to revisit and brainstorm possible reasons.
I have done as described in this thread, set static route to 192.168.254.0, with 192.168.1.200 as the gateway, set the gateway for the cameras to 192.168.254.1, set the dns on the cameras (whether or not necessary to 8.8.8.8 and tried 192.168.1.1). none of this yielded success. I have then put a laptop on the NVR, gave it a 254.xxx address just to make it easier to interact rather than ssh/telnet the camera. on the laptop I set all the same parameters the cameras should have, I then did pinging of other cameras, the gateway 254.1 as well as the router itself at 1.1 all were successful. I was NOT able to ping 192.168.1.200 (nvr lan ip) guessing because the camera thinks its a gateway. in any case I then tried to ping the outside world with no success.
the single thing I did that accomplished mission successful is to change my main router subnet to 255.255.0.0, I did not change the dhcp serving range, I did not change any other attributes of clients on the network nor did I change the ip addresses. this single change now enabled the cameras access to the wan side of my router and effectively out to the web. I have been talking with some network guys, as well as with hikvision (who swear they do not support anything outside of connecting to their poe OR a 3rd party poe switch), and Verizon techs as well as those from the router/modem brand Actiontec. so far NO ONE has been able to explain why simply making the subnet a larger one does it allow the cameras to get out. it seems there is SOMETHING with the routing maybe on the router itself that prevents this maybe some sort of NAT if that's possible?
anyone have any thoughts? again I have done everything in this thread short of going into the camera ssh/putty/telnet but simulated that by using a laptop. I would really rather not have that large of a network if I don't have to but given some of the benefits of having the camera access the outside world I may consider that as my solution albeit a crappy one.
I have done as described in this thread, set static route to 192.168.254.0, with 192.168.1.200 as the gateway, set the gateway for the cameras to 192.168.254.1, set the dns on the cameras (whether or not necessary to 8.8.8.8 and tried 192.168.1.1). none of this yielded success. I have then put a laptop on the NVR, gave it a 254.xxx address just to make it easier to interact rather than ssh/telnet the camera. on the laptop I set all the same parameters the cameras should have, I then did pinging of other cameras, the gateway 254.1 as well as the router itself at 1.1 all were successful. I was NOT able to ping 192.168.1.200 (nvr lan ip) guessing because the camera thinks its a gateway. in any case I then tried to ping the outside world with no success.
the single thing I did that accomplished mission successful is to change my main router subnet to 255.255.0.0, I did not change the dhcp serving range, I did not change any other attributes of clients on the network nor did I change the ip addresses. this single change now enabled the cameras access to the wan side of my router and effectively out to the web. I have been talking with some network guys, as well as with hikvision (who swear they do not support anything outside of connecting to their poe OR a 3rd party poe switch), and Verizon techs as well as those from the router/modem brand Actiontec. so far NO ONE has been able to explain why simply making the subnet a larger one does it allow the cameras to get out. it seems there is SOMETHING with the routing maybe on the router itself that prevents this maybe some sort of NAT if that's possible?
anyone have any thoughts? again I have done everything in this thread short of going into the camera ssh/putty/telnet but simulated that by using a laptop. I would really rather not have that large of a network if I don't have to but given some of the benefits of having the camera access the outside world I may consider that as my solution albeit a crappy one.
Last edited by a moderator:
Your cameras can't even access the internet? The only thing you should need to do for the cameras to have outbound access is:
1) Enable virtual-host
2) Set gateway to 192.168.254.1
Setting a static route just allows you to access the cameras with 192.168.254.x addresses as well.
Right sorry should have said I did turn on virtual host and did set cameras to 254.1 gateway. The ONLY thing I have not done is power off the unit after changes but reboot did take place
alastairstevenson
Staff member
I too see no reason why changing that subnet brings WAN access to life.
The usual reason to expand a subnet is because you are using a wider, contiguous, address range. Which in this case you are not - the LAN and NVR segments are separate, and have a router function (the NVR Linux kernel) connecting them.
On a bigger network, routing information is 'learned' from routing information broadcasts of various types - but this won't be happening on a home network, or a home router (not that I've checked the spec for yours).
The implication of the change is that there is some important traffic that exists somewhere in the /16 range but not in the /24 range. Most odd.
If there are no adverse effects, well and good.
The usual reason to expand a subnet is because you are using a wider, contiguous, address range. Which in this case you are not - the LAN and NVR segments are separate, and have a router function (the NVR Linux kernel) connecting them.
On a bigger network, routing information is 'learned' from routing information broadcasts of various types - but this won't be happening on a home network, or a home router (not that I've checked the spec for yours).
The implication of the change is that there is some important traffic that exists somewhere in the /16 range but not in the /24 range. Most odd.
If you substitute the penultimate word with 'pragmatic' - just go for it.
If there are no adverse effects, well and good.
So my router is fios provided actiontec mi424 revision g. It is connected coax from service and there it converts coax to Ethernet internally with I'm guessing a bridge mode as I don't have the wan port. So it's a modem router. One other thing I have not tried and don't really have the bandwidth to try is plugin the whole system into a true router but yes like you said some traffic passing between the two seems to be the magic but how do I find out what? Any traces I can run to see what happens? This is like the bane of my existence until I figure it out for the sake and good of technology mankind 
@aster1x @alastairstevenson since I have been harrasing both of you, it is only right for me to provide some information found and somewhat confirmed (yet not fixed) this may also be useful for some poor soul like me in the future. Long story short leaving the subnet as a /16 (255.255.0.0) puts the devices on the same subnet. it SEEMS that the modem/router device provided by verizon has somewhat reported issues with NATting devices not on the same subnet as itself. therefore by going to /16 and getting the NVR on the same subnet it does NAT properly and voila. It is still necessary to have the IP routing in place to access the cameras behind the 254.1 gateway (though not quite sure why 254.1 can be reached but the rest of the 254.x can't unless there is a route even though they are technically on the same 255.255.0.0 subnet).
in any case unless someone has a really good suggestion like setting up a vlan or something else, it seems this will be my solution at least until if ever an actual router is purchased to be layer 3 between FIOS and NVR. thank you everyone here who have contributed and entertained my nuttiness, it is truly appreciated. comments welcome
in any case unless someone has a really good suggestion like setting up a vlan or something else, it seems this will be my solution at least until if ever an actual router is purchased to be layer 3 between FIOS and NVR. thank you everyone here who have contributed and entertained my nuttiness, it is truly appreciated. comments welcome
I also agree with the technical reasoning from Alastair. In order to verify if your router has some sort of bug with NATing is to replace it (temporarily?) with something else or even upgrade its firmware. Another way to trace what is really going on in your network is to use wireshark software which can trace everything in your network, however it is a very technical software for network enginners.
@aster1x, unfortunately there is not a spare to test with (though may consider getting a separate L3 device - thought about it a while ago but figured if it ain't broke don't fix it well now it's broke). would wireshark show me dropped packets etc and just a be a more comprehensive version of what trace route does?
Last edited by a moderator:
Wireshark is an extremely detailed network software but requires network communications knowledge to interpret and analyse the information provided. You can check it at www.wireshark.org.
maybe on my list later but for now I am ok with a solution or at least something that give me the bottom line. Hopefully this thread will be very useful for someone as it was for me after all without the guidance here would have never even though of all the items. it is a huge shame though they don't listen to these threads and don't even acknowledge that what we are doing is possible.
Geez I'm a bit tired after reading all that and still a bit confused and I have a networking background.
I have the same problem in that; 7808NI-E2/P at 3.3.4 version.....
1. NVR sends low res motion detect email.
2.The NVR for some reason does not attach any email pictures to Line Crossing...grrrrrrrrr...email but no attachment photo, I haven't managed to get intrusion detection working.
3. My NVR works fine, with time NTP and email, its got the default gateway and DNS of the router 192.168.1.254 255.255.255.0
4. I am working through the same issues/config with trying to get the cameras working with their superior notifications, independently of the NVR having got over all the previous config and workings.
I would have thought that changing the subnet masks from 255.255.255.0 to 255.255.0.0 means that all IP addresses 192.168.1.x and 192.168.254.x are all now just one network, where the router learns and ARPS for host addresses, and remembers what interfaces host port responses came from? e.g. the router LAN port to the NVR learns that addresses on the same network 192.168.254,x are connected via the NVR IP address and interface.
I am trying to avoid converting to one big network 255.255.0.0.
I also get
- numerous illegal logins in my logs.. and the NVR is not even port forwarded from the LAN - believe this is a bug
yah I have no idea what the cause for my issues is with the network but guessing it has to do with the internet provider I use but not sure. at least i know the solution but the understanding from reading quite a bit of forums and threads is that the router/modem i use does not NAT anything not on the main network so by changing to the larger network it makes it one.
as for illegal logins i got that too and no idea what that is. the picture attachment sounds like its an issue with the firmware sometimes does sometimes doesnt, if you reset nvr and wipe hard drive it may help but very odd. i've also found to power off the nvr to help but really this isnt a solution
Hello, New to this forum. @aster1x I have followed your instructions but the camera still can not send an e-mail. Just not sure what I'm missing. The reason I'm trying this method is because my NVR will send an e-mail for Line Crossing Detection but sends an e-mail called Traverse Plane and no pictures. I have a test camera connected to my router and it works great. I receive an e-mail called Line Crossing Detection with pictures attached.
NVR: V3.3.4 build 150811
Camera: V5.3.0 build 150513
Any help would be greatly appreciated.
Last edited by a moderator:
@flyleclair You have not specified us which NVR and camera models you have and what are the four characters in the middle of the serial number that indicate if the camera and NVR firmware are for the western world (market) or for the chinese market. Certain NVR firmware versions have bugs related to the pictures attachements in the emails. It is not clear which combination of firmware versions, NVR model and targetted market are affected. Unfortunately there is no substantial support from HIK Vision. The fact that people try to mix different targetted market NVRs with different firmwares complicates things.
It has also been mentioned in the forum that firmware problems (not neccessary bugs) are rectified simply by rebooting the NVR or camera several times OR by simply reinstalling the same version firware through the TFTP (seems to be the most reliable method) firmware upgrading process. In a nut shell firmware quality and support is a mess.
My advice: if you can identify in the forum even a single report of your own combination of hardware and software components operating successfully what you are trying to do, then you have a genuine problem. Usually there is a fix mentioned in the thead. Your problem is well known and has been discussed in the forum at several threads (keep reading!!!).
If a systematic fix has not been discussed then you do not have a problem, we all have the problem and it is called BUG!!! (joking).
My instructions technically are correct. Keep looking (as in keep ... walking)!!
It has also been mentioned in the forum that firmware problems (not neccessary bugs) are rectified simply by rebooting the NVR or camera several times OR by simply reinstalling the same version firware through the TFTP (seems to be the most reliable method) firmware upgrading process. In a nut shell firmware quality and support is a mess.
My advice: if you can identify in the forum even a single report of your own combination of hardware and software components operating successfully what you are trying to do, then you have a genuine problem. Usually there is a fix mentioned in the thead. Your problem is well known and has been discussed in the forum at several threads (keep reading!!!).
If a systematic fix has not been discussed then you do not have a problem, we all have the problem and it is called BUG!!! (joking).
My instructions technically are correct. Keep looking (as in keep ... walking)!!
Last edited by a moderator:
@aster1x My NVR is the DS-7608NI-E2/8P as mentioned in the title of this thread. The 4 characters in the middle of the serial number are AARR.
My Cameras are model number DS-2CD2332-I.
To get mine going I had to make gmails "less secured apps" turned on. Did this several times as it kept reverting back to off on its own. Double check this.
Without this feature being turned on, no logins will be accepted by gmail.
https://www.google.com/settings/security/lesssecureapps
Without this feature being turned on, no logins will be accepted by gmail.
https://www.google.com/settings/security/lesssecureapps
Hi there from Australia,
I have a Hikvision DS-7608N-E2 / 8P (hacked version thru Aliexpress)
Build is V3.3.2 build 150522
Im trying to get motion detection (of any variety) working with email attachments, but to no avail
The camera is DS-2CD3345-I
I can access the cameras externally (as I have two network cables running from NVR to router).
I have email address/password all set up, and tested. (test emails sent OK).
However, when camera detects motion, the camera shuts down. If I'm viewing through IVMS, the vision drops. Any recording in the NVR stops for 2 mins or so, for that camera (not the other inside 2). The webpage logged into camera also goes unresponsive until the camera reboots.
Obviously, I cant get the NVR to send the email attachment, as it doesnt work in 3.3.2
Any thoughts? Can I update the 3.3.2 NVR to 3.3.4 I know someone did in this thread, but not sure if they had hacked firmware. Happy to go ahead with that if it's feasible.
Thanks in advance. FlyingRain.
I have a Hikvision DS-7608N-E2 / 8P (hacked version thru Aliexpress)
Build is V3.3.2 build 150522
Im trying to get motion detection (of any variety) working with email attachments, but to no avail
The camera is DS-2CD3345-I
I can access the cameras externally (as I have two network cables running from NVR to router).
I have email address/password all set up, and tested. (test emails sent OK).
However, when camera detects motion, the camera shuts down. If I'm viewing through IVMS, the vision drops. Any recording in the NVR stops for 2 mins or so, for that camera (not the other inside 2). The webpage logged into camera also goes unresponsive until the camera reboots.
Obviously, I cant get the NVR to send the email attachment, as it doesnt work in 3.3.2
Any thoughts? Can I update the 3.3.2 NVR to 3.3.4 I know someone did in this thread, but not sure if they had hacked firmware. Happy to go ahead with that if it's feasible.
Thanks in advance. FlyingRain.