This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I want to separate networks in my house and currently have a linksys router as the primary and is the one connected to the modem and would like to have this R8000P as the secundary. I am guesing the method to use to separate networks would be a LAN-WAN topology, can anyone verify this and what will be the settings that I need to change on the secundary router?.
2.-Connected Netgear's Internet yellow port to Linksys's (Primary router) LAN port.
This way there was a conflict because both routers had the same LAN IP segment but the
Netgear Router changed its LAN IP to 10.0.0.1 automatically (but had to powercycle the unit) and 10.0.0.2 as the starting IP address.
3.- Powercycle Netgear router
The Linksys (Primary) asigned a 192.168.1.x to the Netgear internet IP address.
The Linksys as I mentioned before is the one connected to the modem (outside world).
The goal was to keep two separate LAN's with different SSID's and passwords and with the steps followed above I was able to achieve the goal.
I also tried changing the Netgear's (Secundary) LAN IP segment to 192.168.2.1 and also works. Note that this change in the IP address was done before making the physical connection LAN-WAN.
Why? Is there some actual problem which you are trying to solve? It might help if you started at the beginning, and explained what you're actually trying to do, rather than asking how to implement some particular "solution" to whatever problem you think that you have.
> [...] I am guesing the method to use to separate networks would be a > LAN-WAN topology, [...]
What, exactly, does "a LAN-WAN topology" mean to you? (Inventing your own technical terms can produce more confusion than clarity.)
> [...] can anyone verify this and what will be the settings that I need to change on the secundary router?.
That all depends on what you want to do, and how. Bear in mind that cascading routers can cause problems ("double NAT") for devices connected to the inner router. Configuring the second router as a wireless access point can provide one unified LAN with no such problems.
When you say seperate are you talking completely seperate as one had nothing to do with the other?
Also how are you connecting to the internet?
Good questions.
The Internet one is important. If you want both networks to connect to the same Internet service, and to use the same modem, you'll have to be careful to avoid the two networks fighting each other to control things.
I want to prevent the devices conected to the netgear R8000P (secundary) commuicate with the devices connected to the Linksys (Primary). A couple of examples are: I dont want to cast to the other tenant's chromecast or I dont want the other tenant send prints to my wireless printer all these by mistake.
We need both routers have internet access but there is only one ethernet port on the modem plus the ISP provider only provides one IP.
The primary router (Linksys) connects to the modem.
Here is some information I found in Linksys's website:
You could follow those instructions. They seem pretty straightforward, but who knows if the R8000P will play ball?
If your aim is to keep the wifi networks separate, then using unique SSIDs and passwords would be an option.
In that case, you could use the R8000P as an wifi access point. Give that SSIDs and passwords that only you know and the neighbour won't be able to get at your devices.
Ok. Subject to the usual ("double NAT") problems for incoming connections to devices on the inner network, you should be able to connect the WAN/Internet port of the second (Netgear) router to a LAN port on the first (Linksys) router, with no special configuration required. The second (Netgear) router should choose a LAN subnet which is different from its WAN subnet (the Linksys LAN subnet), so accidental connections between devices on the two subnets should not be a problem.
Note that this isolation is partly voluntary. _Intentional_ connections from devices on the secondary router LAN to devices on the primary router LAN would still be possible. To make possible connections from devices on the primary router LAN to devices on the secondary router LAN, you'd need to add a (probably static) route on the primary router.
> If your aim is to keep the wifi networks separate, then using unique > SSIDs and passwords would be an option.
If you want only your own devices to connect to your own router, then different SSIDs on the two routers is a _requirement_, not an option.
> In that case, you could use the R8000P as an wifi access point. Give > that SSIDs and passwords that only you know and the neighbour won't be > able to get at your devices.
Not really. If one router is configured as a wireless access point (WAP, what that Linksys doc calls a LAN-LAN configuration), then there is only one LAN, and all devices share it. The only "isolation" in such a configuration is a restriction on which devices can connect to which wireless access point (the one in the main router, or the one in the WAP-only WAP). Once a device has joined the (single) LAN, using either wireless access point, it will be on the same (single) LAN as every other device, no matter whose radio it's using. This is exactly what you don't want.
2.-Connected Netgear's Internet yellow port to Linksys's (Primary router) LAN port.
This way there was a conflict because both routers had the same LAN IP segment but the
Netgear Router changed its LAN IP to 10.0.0.1 automatically (but had to powercycle the unit) and 10.0.0.2 as the starting IP address.
3.- Powercycle Netgear router
The Linksys (Primary) asigned a 192.168.1.x to the Netgear internet IP address.
The Linksys as I mentioned before is the one connected to the modem (outside world).
The goal was to keep two separate LAN's with different SSID's and passwords and with the steps followed above I was able to achieve the goal.
I also tried changing the Netgear's (Secundary) LAN IP segment to 192.168.2.1 and also works. Note that this change in the IP address was done before making the physical connection LAN-WAN.
