Security camera linking remotely to NVR

[CapLeaker]

I've got already a 16 port NVR installed at a certain location. The building owner wants to add 4 IP cameras on a different building 500m away from the main building.
My way going about is to install the cameras on the off site building, connect them to a 8 port POE switch, install a wifi bridge and plug that into that POE switch too. That should do the remote side. Easy.

The main building should have the other end of the wifi bridge.

Did any one try to hook a wifi bridge staight up to the NVR's camera POE port?
I do know that usually the wifi bridge is hooked up to a switch together with the NVR's internet port. But why not connecting the bridge directly to the NVR's camera port?
Never seen anything or anyone doing it that way.

[diif]

What NVR are you using that allows you to connect more cameras than ports, or are less than 12 cameras being used already?

[CapLeaker]

Yeah, forgot to mention it's a Northern N2 16 port NVR. Only half of them are currently used, The plan of thought was to connect one end of the bridge right to the NVRs POE port where the IP cams hook up to. Never heard anybody doing it this way, but I thought it wouldn't hurt to try

i squiggled something quickly up…

[diif]

I would think it is down to the software on the NVR, I was reading that something similar has been done using a hikvision NVR.

You might need to set static IPs of the new cameras perhaps.

[stj]

do you have line-of-sight between the buildings?

[CapLeaker]

Line of sight for the wifi bridge, yes. This should work for one remote cam for sure, interesting question is, does it also for 4 cams, because they end up on one port of the NVR.

[stj]

the recorder is going to have a hard limit based on cpu, ram etc.
the port itself is probably fast enough - i presume it's gigabit.
if not you may have to look into the stream bandwidth from each camera and if it's an option maybe drop the resolution or framerate

[CapLeaker]

CPU, RAM on the NVR shouldnt be a problem. The NVR has 16 ports and with the 4 new CAMs it would be only having 12 in total. So there is room for 4 more CAMs after this expansion. I think the POE ports run on 100mbit.

[ant3202]

I had deployed on one site before, using ubiquiti, with parabolic antenna

most had raised a good point is LOS


normally my concern is lighting strike on the pole which can fry those connected devices, thus some sites we do this:

Main Office
Customer Network > Customer Network Switch > Fiber Media Converter > Fiber Cable > Fiber Media Converter > Power Injector > Parabolic Antenna

Remote Site
Outdoor Antenna > Power Injector > Fiber Media Converter > Fiber Cable > Fiber Media Converter > Customer Network Switch > Remote Site Network



so far I had observed from other setup from other vendors .. like they are using like,


engenius long range
https://www.newegg.com/global/sg-en/...9uNSTNYdPTcLJQ

mikrotik long range

[stj]

i'm not sure 100Mb is enough for 4 streams - maybe but it depends on the resolution and framerate
if it's compressed it will also depend on how much of the image is static and how much changes

[CapLeaker]

Not worried about lightning as I got proper lightning protection. I did a few WiFi bridges before with zero problems that ran over 10 years on high points only to get replaced by me again in order to ged faster connections.
What I haven't done yet is to put multiple cam streams down one wire straight to the switch POE part of the NVR. In theory it should work, unless the POE switch with its own router part cannot handle more than one IP per port.

[CapLeaker]

Just got around to this again. I tested this configuration yesterday on the bench and this plan as in my post #3 didn't work out. The POE ports on the NVR do NOT allow multiple IP addresses on a single POE port. I could see all the cameras on the list, but only one was connected. I could select a different one, but then the first one got disconnected. Unplugging the connection from the bridge to the POE ports over to the internet side of the NVR through a network switch worked fine as kind having 4 cams through the wifi bridge and going to the NVR. Only problem with it is I need four 192.168..xxx.xxx addresses.
Other than that, it works perfect.

[CapLeaker]

Well, after laying a total of about a 1000ft of shielded, direct burial CAT6 through the building for 4 cams and wifi bridging it to the main building where already a 16 port NVR exists, it works absolutely perfect. Challenges were the crazy 24 feet ceilings.

[Henryko]

I haven't tried connecting a WiFi bridge directly to the NVR's camera POE port myself, but it seems like a reasonable experiment. Usually, the bridge goes to a switch with the NVR's internet port, but connecting it straight to the POE port could work if it's just for the cameras.

[CapLeaker]

I haven't tried connecting a WiFi bridge directly to the NVR's camera POE port myself, but it seems like a reasonable experiment. Usually, the bridge goes to a switch with the NVR's internet port, but connecting it straight to the POE port could work if it's just for the cameras.

Well, it does and does not. It works if you do one camera. But the NVR is unable to assign more than one IP on the camera ports. That means if you put 4 cameras on the WiFi bridge and plug it into the NVR camera port all you get is one cam. The other 3 are there, but you can only connect to one at a time.

My NVR cam extension is getting even further extended soon. Interesting thing is that now the line gets extended another 300 ft with coaxial cable. So I need some MoCa 2.5 adapters. This thing is getting crazy!

[stj]

i just fixed an NVR - SWAN 8 input.
cpu fan had seized after 7 years of 24/7 running, not bad for a SUNON 40mm!!
also did a recap - it was full of crap as usual and replaced the thermal pad with MX4.
after new caps & fan - good as new if not better.

[CapLeaker]

i just fixed an NVR - SWAN 8 input.
cpu fan had seized after 7 years of 24/7 running, not bad for a SUNON 40mm!!
also did a recap - it was full of crap as usual and replaced the thermal pad with MX4.
after new caps & fan - good as new if not better.

Nice fix stj! I've done last year a Northern 32 cam input NVR that was 8 years old at that time. Replaced a few caps in the power supply and she is still working A1. Mine is a 8 input cam system, but I swapped the fans out for Noctua's from the get go, I wasn't going to have it listening to the fan noise. Works great! I had to reboot it once, but that was it.

[stj]

no fan noise on this, it uses a low rpm fan.
probably why it lasted 7 years

[sam_sam_sam]

Well, it does and does not. It works if you do one camera. But the NVR is unable to assign more than one IP on the camera ports. That means if you put 4 cameras on the WiFi bridge and plug it into the NVR camera port all you get is one cam. The other 3 are there, but you can only connect to one at a time.

Is there a workaround for this because I am following this post for knowledge and information about what can be done

[CapLeaker]

Is there a workaround for this because I am following this post for knowledge and information about what can be done

Maybe a firmware update? Problem is that you can't put 16 cams on a 100Mbit LAN. However, 4 or 6 is no problem at all at that speed. The only thing that you can do is like I did. Put the NVR on a internet switch, put the Wifi bridge on the same switch, let the router assign IP's and pick up the CAMs from the LAN side with the NVR. I did assign static IPs to those cams on the LAN. Other than that it works perfect. Have it running like that for months now.

Meanwhile I got another new project. Installing a full blown RX / TX ADSB system, the commercial version which requires a yearly license. Lets see how that goes. the other MOCA ethernet over coax expansion is on hold at the moment until I got this sorted.