I see many issues with that. Your network IT person should have warned you off. Sorry but why would have me duplicate the first quarter or a networking course.
As to the rest sure, why not. But plan your channels and let it auto select channels. 802.11n with its 40 MHz OFDM is sometimes not a good idea. You can google WiFi channels to see why. I pull back to 802.11g to get more coverage with multiple WAPs. You are turning routers into WAPs.
I am setting up a network for some pro audio equipment at a large outdoor venue. My plan is to use 2 cheap Netgear routers with their wireless turned off, DHCP turned off and basically as switches connecting a few computers and pieces of equipment together, all with static IP addresses in the same subnet.
I then will have a TP-Link Archer C7 broadcasting WiFi for another computer and a couple iPad/Android devices to connect (again DHCP turned off and static IP)
I've got it setup so each of the three routers has a different IP address, is there anything else I need to setup aside from just connecting them all together with their LAN ports?
As a 2nd question, sometimes our cables get damaged during the week (we are setup for 2 months) we will be running 2 cables to each position, as long as I have ports available would there be any downside to plugging in both cables at the same time? Would it create any sort of network traffic/data loop?
Any other advice I should follow for the best coverage and data throughput? Honestly I shouldn't need too terribly much since the data is all fairly light weight control information but in the past we have had it bog down some in heavy use
Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic