<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Brad,</p>
<p>I'd approach this in a very different way.<br>
Ask the customer to pickup an extra Network Switch.<br>
Get them to ply the camera (or cameras) in question into the
switch, and also a cable between the switch and NVR.</p>
<p>Then from your desktop simply setup some ssh port forwards
between you and the remote linux system with the individual
cameras and NVR as targets.<br>
You will likely need to also run something along the lines of <br>
ip address add 192.0.0.x dev eth0<br>
on the remote linux box to allow it to "see" the camera network.</p>
<p>Advantages of using this method<br>
</p>
<ul>
<li>You won't risk disturbing the capabilities of the NVR<br>
I've seen quite a few of them that run very short of cpu and
memory.<br>
So much so, that running an extra process can cause issues with
recording</li>
<li>No need for heavy protocols to connect to the remote linux
machine, <br>
simply use a direct ssh connection and some port forwards<br>
</li>
</ul>
<p></p>
Disadvantages<br>
<ul>
<li>The only downside, and it's the obvious one, <br>
is that the customer needs to have an extra switch,<br>
and be able to plug/unplug some network cables.</li>
</ul>
<br>
Regards<br>
<div class="moz-signature"> David Godfrey<br>
SB Tech Services<br>
<a class="sig1" href="tel:+61437286200">mb: +61 437 286 200</a><br>
<br>
<div class="sig"> <span class="left"> <span class="pulseit">chat:</span>
</span> <span style="float: right;"> with <em>dcg_mx</em> at<br>
<a href="http://riot.im/app/#/room/#sbts:matrix.org">#sbts:matrix.org</a>
(Computer)<br>
<a href="http://matrix.to/#/#sbts:matrix.org">#sbts:matrix.org</a>
(mobile Device) </span> </div>
<br style="clear:both">
<br>
</div>
<div class="moz-cite-prefix">On 21/08/17 14:42, Brad Campbell wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8a3e6b4b-7716-6dff-1a79-f06c74823895@fnarfbargle.com">G'day
all,
<br>
<br>
Just putting this out there as I looked for solutions and didn't
find anything workable.
<br>
<br>
I'm doing some remote configuration on a system I have no physical
access to in order to help someone out.
<br>
<br>
This is a cheap Chinese Hikvision NVR. I need to get access to one
of the cameras behind it. The NVR is on a 192.168.0.0/24 network
and the cameras are on a 192.0.0.0/24 network on the NVRs PoE
switch. I can get access to the network via a Linux machine and
OpenVPN.
<br>
<br>
If the cameras are using a native protocol the NVR provides a
dodgy internal port map that allows you to get access to the
cameras web interface. Unfortunately the camera in question uses
another protocol and thus the NVR won't let me near it.
<br>
<br>
I have access to a telnet shell on the NVR, but the internal
version of Busybox doesn't really have anything useful (except
tftp!).
<br>
<br>
So, tftp a pre-compiled busybox binary (found on the busybox site
to same me the effort) to /tmp. Now use the busybox tcpdsvd to set
up a listening port, and run netcat on connection.
<br>
<br>
./busybox-armv6l tcpsvd 192.168.0.220 8080 ./busybox-armv6l nc
192.0.0.13 80
<br>
<br>
Boom. Connect to the NVR on port 8080 and it gets redirected to
the camera on port 80. Win.
<br>
<br>
Alternatives gratefully solicited. Oddly enough this is something
that comes up from time to time and I seem to find a different
method every time.
<br>
<br>
_______________________________________________
<br>
PLUG discussion list: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.plug.org.au/mailman/listinfo/plug">http://lists.plug.org.au/mailman/listinfo/plug</a>
<br>
Committee e-mail: <a class="moz-txt-link-abbreviated" href="mailto:committee@plug.org.au">committee@plug.org.au</a>
<br>
PLUG Membership: <a class="moz-txt-link-freetext" href="http://www.plug.org.au/membership">http://www.plug.org.au/membership</a>
<br>
<br>
</blockquote>
<br>
</body>
</html>