I have a fully routed network, I ping my Client at 6 hops away in 4ms.
I ping 64.233.183.147 (http://www.google.com), this gives me 91ms in average. Google is 20 hops away from my PC.
Probably dial up is not so much slower, for a ping. Satellite is more like 300-400ms, for fast links!
As you can see, the amount of hops in your properly configured network is a minor issue and hardly noticeable.
My network speed is 36Mbps at the slowest link, for data transport. (ping is very little data, the time measured is the time it takes to receive that little package back by its source after its visited the recipient. Data, big data, like files, pictures or streaming data, needs more then just a fast ping time. It also needs capacity. It´s like driving a motorbike through a small alley, you can still make high speed. Now try to push 1000 motorbikes through that same alley! You need a big highway now to keep the data flowing!
I use back haul units that are actually a client (station mode) of a ´higher´ AP. The cards can handle that and for the AP it´s just a client with more traffic then the other ´real´ clients. But by the time an AP gets too many clients it might be wiser to create a separate back haul link to the remote location. When I´m reaching 30+ clients it´s time to plan a separate back haul link. This is both for redundancy reason as well for CPU usage of the AP.
Most secure and redundant would be to have all radio´s in separate boxes, in separate masts (lightning strikes!) and have each box a dual function, so it can take over a function of the other ´sister´ nearby. This can even made fully automated fail over, but it needs a bit more thinking and planning and off course costs!
I use MT routerboards and I have a really big number operator as my friend and both me as him have a very low failure rate of boards in a production environment. Biggest risks are probably coming from outside; lightning, static discharges, (forest)fires, power loss of the host (house or whatever) and may be in your case, vandalism. All these things have their solutions or workarounds. The boards themselves seem to have eternal lives under normal conditions…
In your case I would work with a backhaul system all the way up to the end as you main connection in a routed network with seperate AP’s for the clients. The different radio’s can still be shared in one box. For instant, rb333 can have three cards. One will be the ´station´ looking at his AP for the Backhaul. The second will be the AP for the the backhaul link towards the next ´station´. And the third can serve as an AP for clients. As long as you have not more then 40 clients on each AP, and or very big traffic load this should be no problem for the boards.
Each ´station´ should also be able to log into the ´client serving AP´ higher up the link, in case its higher backhaul AP would fail. Work with access lists and connect lists.
Pure radiowise spoken, each unit would have now two AP’s and one client radio.
Give each backhaul link its own network, as each AP with clients in one network. Now by setting the proper default gateway’s and backup gateways together with the backup radio´s in the connect and access list you have a pretty reliable, and fast system.
I try to have all my radio links in the region of -60 to -75dBm which give me basically at least 36Mbps connection speeds. Since we have simplex connectivity and traffic overhead etc. this means a ´real´ network speed of 20, 25Mbps is possible.
General network speed comes more down to proper radio link configuration, proper configuration of the different traffic prioritizations if the links see heavy traffic, etc.
And there is much more to be ´fine´ tuned to get the max. out of the network speed.
But, to come back to your first question, the amount of hops is really of no issue.
rgds.
Rudy
. Start with BH 1 (in bridge mode With every AP in between has the possibility to take over a backhau