Wireless Access Point

To give better wireless coverage I've pressed into service an unloved cable router, connected via CAT5e from the main router. It does the business and in actual fact wired devices are also connected to this "remote" router. The primary LAN is 192.168.79.xxx with those devices connected to the "remote" router being allocated IP address in the range 192.168.82.xxx.

The primary router sees the remote router as 192.168.79.17 so it is possible to login to the remote router using that IP address and view the DHCP table.

Let as say a CCTV device is connected to the remote router and is allocated the IP address of 192.168.82.12. Now from a computer on the primary LAN with an IP address of 192.168.79.27 I am seeking a method of logging onto the CCTV device. Obviously no problem if the computer was connected to the '82' LAN but I can't work out the syntax to use from the '79' LAN.

Am I trying to do something that is not possible or is there a solution that I can adopt? Yes I could make the two LANs both use192.168.79.xxx but I prefer not to do that unless absolutely essential to do so.

With many thanks for any responses received.

You could adjust the two routers to use the same subnet, just start one half way through the IP range, and set the other to use the lower half of the IP range.

Or you could setup a NAT using a specific IP address on the main router to point to the IP of the camera.

You could also turn off DHCP on the second router, so the primary router issues all the addresses (aka bridge mode)

Hi,

If you change the subnet mask to 255.255.0.0 on both routers (and PC's/clients if you are not using DHCP), that should allow you access, or as previously suggested split the DHCP between the 2 routers and use the same subnet. Either way should work but depends if you want different subnets?

Hope that helps?

Dave

Very helpful suggestions made by you Guys; Thank you SO much.

When doing this (I've even done it with spare BT Homehub 5s) I don't use the routing capabilities of the slave router, I don't want cascaded NAT etc.

Just disable DHCP on the spare router, assign it an IP in the existing subnet in case I want to access it, and connect everything to it's LAN ports ignoring the WAN side.

As others have said, make it simple and have just a single DHCP server on the main router.

I have several additional WAPs on my network - all are routers with DHCP turned off. I can then connect wired or wireless to them and if I move from one wireless connection to another my IP remains.

I have my network set to allocate xxx.xxx.xxx.64 to xxx.xxx.xxx.127 dynamically and on request by PCs, tablets, phones &c. The individual WAPs/slave routers are .160 .170 .180. .190 - easy to remember. Other devices such as printers are given fixed IPs in the .200 to .240 range.