# SNI-Based Camera Routing From NVR

- Link: https://www.agilicus.com/anyx-guide/sni-based-camera-routing-from-nvr/
- Published: 2024-10-17T16:18:20+00:00
- Author: Don Bowman

1. [Home](https://www.agilicus.com/)
 2. SNI-Based Camera Routing From NVR

![surveillance-camera](https://www.agilicus.com/www/8d280196-surv-camera-1024x622.
png)

DIRECT ACCESS

---

## SNI-Based Camera Routing From NVR

Got Starlink? Got Camera? Got external NVR? We got your back.

[CONTACT](https://www.agilicus.com/contact-us/)

## Setup SNI-Based Camera Routing From NVR

Imagine you have a network video recorder (NVR) which is located centrally. And,
you have a remote site with a surveillance camera that speaks HTTPS (the below instructions
are not suitable for RTSP). The remote site is served via Starlink, which has no
possibility of inbound access due to NAT.

If you have an architecture where you normally use a fixed-IP and a port-forwarding
system, you might find SNI-based routing can be an appropriate substitute. This 
example gives some tips on setting this up.

### High Level Steps

 1. Signup ([https://www.agilicus.com/anyx-guide/signup/](https://www.agilicus.com/anyx-guide/signup/))
 2. [Create](https://www.agilicus.com/anyx-guide/agilicus-connector/) connector
 3. [Create](https://www.agilicus.com/anyx-guide/product-guide-applications/) Web Application
 4. Modify Network to be ‘Expose as Hostname’
 5. Configure NVR to use external name.

### Create Web Application

Select Resources/Applications/New, give the camera a hostname (this needs to be 
a valid Internet name). Select ‘from my site via onsite connector’, select the connector
you created above.

For the upstream, the IP (or hostname) will be the *internal* one, e.g. what the
Connector would see or talk to. You may need to select one of “No-TLS”, “TLS-AND-
VERIFY”, “TLS-AND-NO-VERIFY”, depending on whether your camera is setup with encryption/
https.

Now apply permissions to yourself. At this stage you can test the camera (e.g. open
your mobile, turn off WiFi, open https:///profile.__MYDOMAIN__/ and then select 
the camera, or, navigate directly to its url, https://<my-camera>.__MYDOMAIN__, 
where my-camera is the name you gave it, and __MYDOMAIN__ is the domain you chose
when signing up to Agilicus (its in the top URL bar of your admin web interface).

![image](https://www.agilicus.com/www/f6c5806b-image-1024x889.png)

![image](https://www.agilicus.com/www/b3099fbe-image-1024x718.png)

![image](https://www.agilicus.com/www/c4751ddb-image-1024x665.png)

![image](https://www.agilicus.com/www/a1607e7d-image-1024x853.png)

![image](https://www.agilicus.com/www/1e43263a-image-1024x831.png)

![image](https://www.agilicus.com/www/f39728ee-image-1024x875.png)

### Modify Network

At this stage we will enable direct routing (disabling the firewall). We do this
by finding the backend network created above, selecting ‘expose as hostname’. Note
the exact hostname given, something.networks.__MYDOMAIN__. This should now be available
for your NVR to connect to.

![image](https://www.agilicus.com/www/da7c9508-image-1024x802.png)