<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Brad,</p>
<p>Well, "That Sucks"</p>
<p>I've had good success with extra switches in the past :-)<br>
</p>
<div class="moz-signature">
<style>
div.sig {
border: 1px solid black;
height: auto;
float: left;
padding: 1em;
padding-top: 0.5em;
padding-bottom: 0.5em;
}
a.sig1 {
padding-bottom:1em;
margin-bottom:1em;
}
span.left {
width: 4em;
float: left;
}
span.pulseit {
-webkit-animation: mymove 1s infinite; /* Chrome, Safari, Opera */
animation: pulse 2s infinite;
}
@keyframes pulse { 50% {font-size: 0.9em;} }
</style> Regards<br>
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 23/08/17 09:31, Brad Campbell wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1b739e84-6982-cff7-5ed6-bfacdeb8a8b1@fnarfbargle.com">G'day
David,
<br>
<br>
I had already dropped them off a switch the week prior, and we
tried exactly what you are suggesting prior to doing it the way we
did it.
<br>
<br>
The reason that didn't work is the NVR in question has 8 PoE
ports. They are managed by an internal switch in the NVR, and the
NVR is individually aware of what is plugged into each port. When
the camera is plugged into a port, the NVR configures it up and
assigns it the recording channel associated with *that* port.
<br>
<br>
The NVR isn't capable of seeing more than one device on a port
because it uses some trickery with the port to assign the
recording channel on the unit. Thus putting the cameras on an
external switch prevents the NVR from being able to see them, and
it can't associate them with their normal channel numbers.
<br>
<br>
There is a tech note that says this *should* work, but in typical
Chinese junk hardware/software fashion it *doesn't*.
<br>
<br>
It's all part of the "make it plug and play for the customer"
perversity that brings with it all sorts of limitations.
<br>
<br>
I'm pretty familiar with these NVRs (unfortunately), so I knew
there wasn't an issue with memory or CPU.
<br>
<br>
<br>
On 22/08/17 18:13, David Godfrey wrote:
<br>
<blockquote type="cite">Hi Brad,
<br>
<br>
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
<br>
also a cable between the switch and NVR.
<br>
<br>
Then from your desktop simply setup some ssh port forwards
between you
<br>
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.
<br>
<br>
Advantages of using this method
<br>
<br>
* 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
<br>
recording
<br>
* No need for heavy protocols to connect to the remote linux
machine,
<br>
simply use a direct ssh connection and some port forwards
<br>
<br>
Disadvantages
<br>
<br>
* 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.
<br>
<br>
<br>
Regards
<br>
David Godfrey
<br>
SB Tech Services
<br>
mb: +61 437 286 200 <tel:+61437286200>
<br>
<br>
chat: with /dcg_mx/ at
<br>
#sbts:matrix.org
<a class="moz-txt-link-rfc2396E" href="http://riot.im/app/#/room/#sbts:matrix.org"><http://riot.im/app/#/room/#sbts:matrix.org></a> (Computer)
<br>
#sbts:matrix.org <a class="moz-txt-link-rfc2396E" href="http://matrix.to/#/#sbts:matrix.org"><http://matrix.to/#/#sbts:matrix.org></a>
(mobile Device)
<br>
<br>
<br>
On 21/08/17 14:42, Brad Campbell wrote:
<br>
<blockquote type="cite">G'day all,
<br>
<br>
Just putting this out there as I looked for solutions and
didn't find
<br>
anything workable.
<br>
<br>
I'm doing some remote configuration on a system I have no
physical
<br>
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
<br>
the cameras behind it. The NVR is on a 192.168.0.0/24 network
and the
<br>
cameras are on a 192.0.0.0/24 network on the NVRs PoE switch.
I can
<br>
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
<br>
internal port map that allows you to get access to the cameras
web
<br>
interface. Unfortunately the camera in question uses another
protocol
<br>
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
<br>
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
<br>
same me the effort) to /tmp. Now use the busybox tcpdsvd to
set up a
<br>
listening port, and run netcat on connection.
<br>
<br>
./busybox-armv6l tcpsvd 192.168.0.220 8080 ./busybox-armv6l nc
<br>
192.0.0.13 80
<br>
<br>
Boom. Connect to the NVR on port 8080 and it gets redirected
to the
<br>
camera on port 80. Win.
<br>
<br>
Alternatives gratefully solicited. Oddly enough this is
something that
<br>
comes up from time to time and I seem to find a different
method every
<br>
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>
<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>
_______________________________________________
<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>