Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 1794 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

REDs, DDNS, and NVRs

Allan Miller

Wondering if anyone can help me out.

Trying to configure remote access to some NVRs at some branch locations connected via split tunnel to an XG135 at HQ. I have the NVR at HQ working fine using Sophos DDNS - easy enough - but can't figure out to configure/how to configure the REDs for their own DDNS (since they access the internet directly). I have no need nor desire to route the cam traffic through the XG but am willing to try it if I have to. Any info appreciated.

Pardon the crude PP drawing. The direct connects to the internet from REDs is supposed to represent the split tunnel - I'm sure you get it.





This thread was automatically locked due to age.
  • 0

    REDs do not need their own DDNS. The Interface IP on XG is the "LAN" Interface of the RED. Basically the WAN interface of RED is not needed by the XG, because RED will build up the connection all the time to the XG IP/DNS. 

    Why do you need a DDNS on the RED site? 

  • 0

    Hi  

    If you want to access NVR, it can be achieved by the Standard Unified Tunnel.

    Can you please elaborate a little more about your scenario and requirement?

    What is the purpose of DDNS for RED device?


  • 0 in reply to LuCar Toni

    I don't know that I need DDNS on the REDs, I just can't figure out any other way of remotely accessing the NVRs at the branches via a camera app without configuring DDNS for them without routing all of their traffic through the XG (which I'd rather not do for obvious reasons). I'm looking for any solution that will allow me to:

    -Remotely access the NVRs at each branch location.
    -Avoid tunneling all of the camera traffic through the XG at HQ

    Thanks for replying

  • 0 in reply to Keyur

    I agree that a unified tunnel would allow remote NVR access but I am seeking an alternative method because I do not want to route public-bound traffic from the branches through the XG. I am hoping for a method that maintains the standard/split tunnel configuration.

    I don't have a specific need for DDNS for the REDs - I just can't figure out another way of meeting the customer's needs - remotely viewing the NVR cam streams without routing that traffic through the XG.

    In the current standard/split configuration, the NVR traffic would simply access the internet directly (as it's not local-sourced traffic when a remote camera app on an external network is attempting to stream from them). I'm trying to figure out how to configure the network so that that remote camera mobile app knows where to point (hence the idea of DDNS) to retrieve the stream. As it stands, I don't have a public IP address that points to the NVR traffic unless I point to the public IP address on the branch gateways.

    Each RED is currently getting a 192.169.0.x WAN uplink IP address from an ISP gateway's DHCP. I'm willing to set those gateways to DMZ mode but, at best, I'm just going to get ISP public IPs on the RED WAN uplinks which doesn't help if I don't have DDNS configured to point to that public IP.

    I may have muddied the waters with my DDNS request - I'm just looking for a configuration wherein a remote mobile camera app can access the NVRs at the remote branches without having to route the NVR traffic through the XG (unnecessarily taxing the HQ's internet connection and the XG's resources).

    Thanks.

  • +1 in reply to Allan Miller

    Hi  

    Thank you for providing details.

    I understand your concern that you want to decrease the load on HQ XG and wants to establish communication for CAM and NVRs.

    RED devices are  GUI less and only manged from XG firewall and purpose of RED device to extend the network and connectivity but still manage it from XG.

    Unfortunately, there is no provision of DDNS configuration for RED device. I will check an alternative for your provided network diagram and inform you if I have anything to share.

  • 0 in reply to Keyur

    The only solution would be to replace the REDs with small Desktop XGs. 

    Like Keyur wrote, REDs are only limited VPN boxes with zero touch. 

    XG can setup such things easily and you do not need any subscription to resolve this issue. 

    VPN is included in the base license, so basically buy the box (XG106?) and replace the reds. 

  • 0 in reply to Keyur

    Thank you, sir.

    Sorry for the confusing wording of the question. My logic was that since the RED is routing private traffic to public IP space, the routing might be configurable in some way, even if the config has to be managed/pushed from the XG.

    I'll route the NVR traffic through the XG and hope for the best. If that doesn't work out for the customer, I'll look into swapping the REDs for XG 106s.