This is similar to how I have my Lorex wireless system, but I wanted to ask those in-the-know if I'm going to have problems splitting the system over a wireless network like this. The trick is that one half of the system is in a nearby outbuilding because the house is undergoing renovation. I'll be tapping into the server via remote desktop, & I usually like to keep a live view running on an Android tablet. I just want to make sure I'm not setting myself up for failure here. Thanks, Cotton
It shouldl IF the Range Extender mode of the Archer AC1200 will act like a client and connect automatically to the Archer AC1900. I would also assign unique, static IPs to both routers and to all the cameras, all in the same subnet and all IP's OUTSIDE of the AC1900's DHCP pool.
OR do as below with TP-LINK or Ubiquiti radios. Install a second Ethernet port in the PC (NIC2), put NIC1 on the same subnet as the router (with 192.168.0.1 for its LAN as an example) and put NIC2 on a different subnet (192.168.1.XXX) but same subnet as the 2 radios and all the cameras. This will isolate the cameras from the Internet but allow the BI server access to the Internet for remote access.
You can dial down the transmit power (AP) and the receiver (station) sensitivity since they are indoor and the distance is minimal.The TP-LINK 2.4GHz unit is the CPE-210 ,the 5GHz is the CPE-510. Like the UBNT (Ubiquiti) they communicate with each other with a proprietary protocol which increases their speed and reliability.
Their terminology and setup is different from UBNT but ultimately provide a similar function.
I installed my NVR at a location that was practically impossible to run ethernet cable to. So for a couple years I used a spare router setup as a Wireless Bridge (with DD-WRT firmware installed) connected to my NVR system with 8 cameras. I had good WiFi signal at both the NVR and my modem/router. Worked great!
I'm going to have to actually connect everything before I can say whether or not it works, though I'm doubtful because the secondary router isn't listed as a connected device on the client list of the primary, and I have to be connected to that second router in order to see all the devices connected to it. I'm going piecemeal building this new system, & I've only just begun what I know will be a slow process. In all reality, I may actually finish my house & sell it with the Lorex setup before I finish getting all the components together for the new system - though I'm afraid that if karma is for real, then I might be struck by lightning for giving someone that Lorex system. XD However, I've already bought the BI software, & am now shopping for an i7 to put in my antique server. Baby-steps & all, ya know.
