grafix4d wrote

Hi all,

in our small office, we have a subnet as 192.168.1.xxx. On 192.168.1.1 we have the router, on 192.168.1.5 our fileserver and ERP server our 10 PCs have static IPs from 192.168.1.20 to 192.168.1.29 and I have setup the router so that DHCP server range is from 192.168.1.150 to 192.168.1.200. All working fine.

Last week, a guy installed 20 IP cameras in range 192.168.50.10 - 192.168.50.29 and connected them on a standalone switch (not connected to our router)

How can I connect (what TPlink device to use) the subnet 192.168.50.xxx to our main subnet (192.168.1.xxx) so that we can see that cameras from any PC but also to be able and forward the cameras through our router ?

Thank you in advance

Hi grafix4d

For connect different subnets, you need layer3 switch to set up the layer 3 interface for different subnets, then the switch will generate the routing and the different subnets can communicate thorugh the routing. If your router has layer3 interface, it should be able to do this as well.

grafix4d wrote

Hi all,

in our small office, we have a subnet as 192.168.1.xxx. On 192.168.1.1 we have the router, on 192.168.1.5 our fileserver and ERP server our 10 PCs have static IPs from 192.168.1.20 to 192.168.1.29 and I have setup the router so that DHCP server range is from 192.168.1.150 to 192.168.1.200. All working fine.

Last week, a guy installed 20 IP cameras in range 192.168.50.10 - 192.168.50.29 and connected them on a standalone switch (not connected to our router)

How can I connect (what TPlink device to use) the subnet 192.168.50.xxx to our main subnet (192.168.1.xxx) so that we can see that cameras from any PC but also to be able and forward the cameras through our router ?

Thank you in advance

You didn't provide information about your existing network, at least about root router.

The right solution is to use L3 switch to route your subnetworks (T3700G-28TQ). It is too expensive though.

If you had old TL-ER6120, you could configure DMZ-port for this. Any other device, which supports it, will help.

The alternative one is to use any cheap device with L3 feature, like mikrotik.

The non-cost solution is to change your mask to /16 (255.255.0.0) on the whole network. <- If I were the system administrator of your network, I would definitely choose this solution.