I am setting up my WISP service within the next couple of months, so now’s the time to have someone tell me what I’m doing wrong rather than after I get it in place.
I’m planning on using a WDS bridge from the T1 to my location, AP1, handle my routing here rather than at the T1 location where I have limited access to the location.
Come out of my AP with a dedicated rb333 WDS bridge to the tower, 333 on the tower with r52 or r52h to the water tower in town A, another pair of 333’s and r52’s for a connection to town B at a later time. I plan on having each AP on its own subnet.
Setting it up this way, am I going to have a huge congestion problem at the tower? The tower is only a p2p hop to connect areas I can’t hit from my tower. Eventually, it will likely have its own AP, but that will follow town b.
I’d rather not eat 8+ IP’s routing an extension cord unless there is a definate benefit.
0ldman -
No I am not ‘following you’ around the forum… I just happen to be on the forum being helpful… I have a medium size WISP 1000+ about 1/3 commerical users…I am just passing on what I have learned over the years…
I am confused as to why you WDS link between your T1 and the Tower? Can’t you simply add a single route to AP1 from your T1 interface and let AP1 do all the routing, nat’ing, or masq’ing from there to/from your T1?
If you setup VPN to AP1 then you only need to use a single public IP to access AP1. You simply VPN in to AP1 and from there you just use local addresses to access anything on your wireless network…
There will be congestion at the tower - but with an RB333 you should be able to handle 50+mbps of traffic (turbo mode + solid connection to AP1) 20 -25 mbps (non-turbo mode + solid connection).
Later - as you grow - you can set some queuing in the APs that serve your clients. If you are using client CPEs that allow queuing locally then you can set a lot of that up along w/some firewall rules in the clients themselves to take the load off of your APs and backhauls and ‘main’ router(s).
If you want to ‘talk’ to some folks that have used bridging and are trying to get away from it because of all the issues when used over wireless w/many clients - find ‘wirelessrudy’ or ‘gunzoid’ posts and ask them how much better routed is over WDS / bridged networks…
0ldman -
No I am not ‘following you’ around the forum… > > I just happen to be on the forum being helpful… I have a medium size WISP 1000+ about 1/3 commerical users…I am just passing on what I have learned over the years…
Actually, I was looking forward to your answer.
I am confused as to why you WDS link between your T1 and the Tower? Can’t you simply add a single route to AP1 from your T1 interface and let AP1 do all the routing, nat’ing, or masq’ing from there to/from your T1?
I’ll see what I can come up with as far as addresses on the T1 side. Its not actually a T1, it is a portion of a 10Mb fiber. Aside from the radio on their tower, I have no equipment at that location. That is why I was looking at making that shot as transparent as possible. It seems that a few points (pretty much the p2p shots) in my layout would be so much simpler bridged.
I just happen to be on the forum being helpful… I have a medium size WISP 1000+ about 1/3 commerical users…I am just passing on what I have learned over the years…