I will consider whether I really need to do this or not, but for better or for worse, right now I have it this way. I have a D-Link DIR-655 Router (mainrouter). It has ports as follows:
a) WAN - Cable Modem
b) #1 - NAS
c) #2 - main1
d) #3 - main2
e) #4 - Linksys switch
f) Wireless - Linksys Print Server
The switch is wired as follows:
a) #1 - mainrouter
b) #2 - clientrouter
c) #3 - guestrouter
clientrouter is a Linksys router. clientrouter is wired as follows:
a) WAN - Linksys switch
b) #1 - d-des
c) Wireless - dw-des
d) Wireless - bw-des
e) Wireless - at-des
f) Wireless - bt-des
g) Wireless - aph-des
h) Wireless - awii-des
guestrouter is a Netgear router. guestrouter is wired as follows:
a) WAN - Linksys switch
b) #1 - Cord for guest computer
c) Wireless - Any guests on the network
I chose to have multiple subnets to logically divide up the network into groups depending on the reason for the client.
However, I do not think I have used the right technology to accomplish this, because it's not very reliable. The netgear router needs to be manually unplugged and plugged back in often, but this is normal for it's model. The Linksys router is humming just fine along. When I in the past, tried a Linksys router (the same model as the clientrouter), as the mainrouter, it was unstable all the time. I had to return it (there was no damage or anything, it was just inherently unstable).
This model, the D-Link, is similar, but until now was seeming to be livable for now, at least barely. This one origionally stayed stable for long periods of time, anywhere from 2 seconds to 1 week I'd estimate, although the exact period it'd stay stable for I could not predict yet. When it was unstable, I could get to Internet from the router, but not anything connected to the router (connected in any way). I had to reboot the router to fix the problem, by it's web interface. I could not just release and renew the IP, it had to be a reboot.
But now, it's behavior is changing. Now it loses total network connectivity when it does that, and needs to be manually unplugged and plugged back in. It often doesn't boot right with just one time, so I have counted that the usual amount is 6 times in a row, waiting for it to boot each time, before it works again. But not always, sometimes it will only take 1 time, or sometimes 2, so you need to check what's going on each time, though the lights mainly tell you. Not until the last time, can you use the web interface either.
This is a recent purchase, because my old mainrouter died, and it was working just fine. It was a DIR-615 router, but you cannot get those from d-link anymore. It's too old. I already troubleshooted with the tech support, and we ended up coming to the conclusion that the hardware is probably dying and that's why the new behavior. I could not return it or anything anymore, because it's probably due to using my specific configuration with it that it doesn't work.
Can you either point me to a model of router with similar features that will work in this configuration, if this is one right way to do it, or tell me what a better way to accomplish this dividing is?
a) WAN - Cable Modem
b) #1 - NAS
c) #2 - main1
d) #3 - main2
e) #4 - Linksys switch
f) Wireless - Linksys Print Server
The switch is wired as follows:
a) #1 - mainrouter
b) #2 - clientrouter
c) #3 - guestrouter
clientrouter is a Linksys router. clientrouter is wired as follows:
a) WAN - Linksys switch
b) #1 - d-des
c) Wireless - dw-des
d) Wireless - bw-des
e) Wireless - at-des
f) Wireless - bt-des
g) Wireless - aph-des
h) Wireless - awii-des
guestrouter is a Netgear router. guestrouter is wired as follows:
a) WAN - Linksys switch
b) #1 - Cord for guest computer
c) Wireless - Any guests on the network
I chose to have multiple subnets to logically divide up the network into groups depending on the reason for the client.
However, I do not think I have used the right technology to accomplish this, because it's not very reliable. The netgear router needs to be manually unplugged and plugged back in often, but this is normal for it's model. The Linksys router is humming just fine along. When I in the past, tried a Linksys router (the same model as the clientrouter), as the mainrouter, it was unstable all the time. I had to return it (there was no damage or anything, it was just inherently unstable).
This model, the D-Link, is similar, but until now was seeming to be livable for now, at least barely. This one origionally stayed stable for long periods of time, anywhere from 2 seconds to 1 week I'd estimate, although the exact period it'd stay stable for I could not predict yet. When it was unstable, I could get to Internet from the router, but not anything connected to the router (connected in any way). I had to reboot the router to fix the problem, by it's web interface. I could not just release and renew the IP, it had to be a reboot.
But now, it's behavior is changing. Now it loses total network connectivity when it does that, and needs to be manually unplugged and plugged back in. It often doesn't boot right with just one time, so I have counted that the usual amount is 6 times in a row, waiting for it to boot each time, before it works again. But not always, sometimes it will only take 1 time, or sometimes 2, so you need to check what's going on each time, though the lights mainly tell you. Not until the last time, can you use the web interface either.
This is a recent purchase, because my old mainrouter died, and it was working just fine. It was a DIR-615 router, but you cannot get those from d-link anymore. It's too old. I already troubleshooted with the tech support, and we ended up coming to the conclusion that the hardware is probably dying and that's why the new behavior. I could not return it or anything anymore, because it's probably due to using my specific configuration with it that it doesn't work.
Can you either point me to a model of router with similar features that will work in this configuration, if this is one right way to do it, or tell me what a better way to accomplish this dividing is?