Remote access of security cameras - REVISITED

[amirijaz]

This was started in another thread but thought it would be better to discuss in a new thread.  Some historical discussion on previous generations, but looking for latest info on Gen 5.

Trying to connect a Hikvision DVR to view security cameras remotely.  These are not IP cameras but rather wired through coax to the DVR, which is then connected to the HT2000w. While IPv6 complications, the answer was as follows from the other thread.  Any other comments on making this work?  Any advantage of HN business account vs. consumer account?

"Go to your HT2000W setup page and, under advanced settings, in the firewall section:
-Enable the firewall
-Disable DMZ
-Disable both intrusion detection checkboxes
-In IPv6 rules, add a rule with "::" as the client address (no quotes), TCP, start port 1, end port 1.
-REBOOT THE ROUTER USING THE WEB UI OPTION, then don't change any more firewall settings"

[Liz]

Hi amirijaz,

Welcome to the community and thank you for posting. I'll defer to those who have successfully gotten their security cam systems set up with their HughesNet system. 

Regarding your question about advantages of HughesNet Business vs Residential, our enterprise department which oversees the HughesNet business side does not recommend getting a business account unless you actually need it for your own business, not just for getting an IP address. For anyone considering HughesNet for Business, you can start your research here.

[pswired]

Basically, this is not possible on Gen5 as it currently stands. Configuring the IPv4 inbound port forwards required for a conventional DVR (Hikvision, etc.) will not work due to the CGN layer added to the Gen5 network. Your router's "public" IP is not a public Internet routable IP address.

Hughes does assign a public, routable, IPv6 block to your LAN, but it changes so often that it's useless. Dynamic DNS infrastructure for IPv6 isn't really much of a thing because customer issued IPv6 blocks aren't supposed to change. We're kind of in a pickle until (if ever) Hughes prevents the customer IPv6 blocks from changing.

The solution here is to use a camera system that connects to a cloud service (Ring, Nest Cam, etc.).

[marand]

---

@pswired wrote:

Basically, this is not possible on Gen5 as it currently stands. Configuring the IPv4 inbound port forwards required for a conventional DVR (Hikvision, etc.) will not work due to the CGN layer added to the Gen5 network. Your router's "public" IP is not a public Internet routable IP address.

Hughes does assign a public, routable, IPv6 block to your LAN, but it changes so often that it's useless. Dynamic DNS infrastructure for IPv6 isn't really much of a thing because customer issued IPv6 blocks aren't supposed to change. We're kind of in a pickle until (if ever) Hughes prevents the customer IPv6 blocks from changing.

The solution here is to use a camera system that connects to a cloud service (Ring, Nest Cam, etc.).

So if I switch the network to IPv6 and use a product like Dynamic DNS to 'make' it a static IP I should be able to connect to the cameras?

---

[pswired]

Yes, if you have a way to use a dynamic DNS service to update your IPv6 address, that will work. However, the DDNS client in my Hikvision DVR doesn't appear to be IPv6 enabled. 

[tracerrx]

Sadly the DDNS providers for IPv6 in sonicwalls are also not entirely functional (and maybe rightly so since this is NOT how delegated ipv6 is supposed to work).

At this point the only real solution is for HughesNet to fix the problem.

[marand]

---

@pswired wrote:

Yes, if you have a way to use a dynamic DNS service to update your IPv6 address, that will work. However, the DDNS client in my Hikvision DVR doesn't appear to be IPv6 enabled. 

---

Thanks 🙂

My Hikvision DVR seems to have the IPv6 settings, but they are greyed out. I'll have to see if they can be enabled.