I am setting up a network between 3 branch offices and I would like some kind of input from the experienced users

Current network

Main Office (MO): 192.168.1.0/24
BRANCH1 (BR1): 192.168.2.0/24
BRANCH2 (BR2): 192.168.3.0/24
Since there is no LOS We will be using mountain tops for connection
where

MT1 is near main office ~6 miles
MT2 is between 2 branch offices ~6 miles to each
and MT1 to MT2 is about 35 Miles

Here is my war plan for this network
I am planning to use routerboard 112 at MO, BR1, BR2
and routerboard 532 at MT1 and MT2

I think I will not use nstream due to CPU speed of the boards (did my homework read the forums.)

I would like to route all the traffic instead of bridge
I will use XR5 (600mW) on all interfaces (I will adjust the power at each link accordingly)

MO:
RB112
Lan 192.168.1.254 to current network
Wlan1 192.168.100.2/24 (Client Mode)
6 miles link to MT1

MT1:
RB532
Wlan1: 192.168.100.1/24 (AP Mode)
Wlan2: 192.168.101.2/24 (Client Mode)
35 Miles Link to MT2


MT2:
RB532
Wlan1: 192.168.101.1/24 (AP Mode) to MT1
Wlan2: 192.168.102.1/24 (AP Mode) to BR1
Wlan3: 192.168.103.1/24 (AP Mode) to BR2

BR1:
RB112
Wlan1 192.168.102.2/24 (Client Mode)
6 miles link to MT2
Lan 192.168.2.254 to current network

BR2:
RB112
Wlan1 192.168.103.2/24 (Client Mode)
6 miles link to MT2
Lan 192.168.3.254 to current network


I use each Wlan for dedicated link because I think pinching couple of hundred will give me dedicated full speed to each branch.

Questions
1: should I use strictly 532 board at each location instead of 112?
2: what is my expected speed between MT1 and MT2 (I am expecting this to be my bottleneck)
3: How the heck I will point the antennas to each other with bare eyes at 35 miles apart
4: Any better plans you have?
5: I might bump 35 mile link to 32.5 dbi's (Should I)???
I know it is going to be overkill but I will use 29dbi parabolic grid antennas at all places(yes even 6 mile links) I got a great deal on them

Thats very straightforward to do , the only problem i could see is the 3 radios in MT2 with one long link might cause a problem . Maybe the new faster boards coming out might be available on time for this ?

Maybe they would like a full duplex Nstreme2 link all the way instead ?

Thx for Quick response.

I have about 2- 3 weeks to plan implement and test/demo the system
would you recommend RB200 s on top of Mountains

double antennas would cost too much for the mountain tops as ~$500 per antenna Quote by American tower.

yakcora -

bushy has it mostly right. You can't use 3 XR or SR cards in a 532 - period...power requirements can't be met by the 532 power supply - 2 SR cards are the max.

You might be able to use one XR or SR card and maybe two MT R52 cards for the branch offices especially if you are using high gain - 29dbi - 'dish' antennas. Personally I'd use two 532s at your MT2 location. Use a larger box or use two separate smaller boxes - you'll need the appropriate number of power supplies as well and a little modification of your routing plan but I think you can handle that ok. I would also use the SR vs the XR cards. SR cards have a proven track record, the XRs are brand new....

1) I would, the added few bucks were worth it to me.

2) About 25Mbps will be the top end - you might hit 30Mbps but no more.

3) Aiming antennas at 35 miles is pretty easy actually.... At 35 miles the cone of the signal is pretty broad. There is a lot of radio mapping software out there - most are free - here's one; http://www.cplus.org/rmw/

Make a quick map with your locations, include the beamwidth of your 32 db antennas. That will show how much play you have and the general direction to point things relative to the geography. Next get your long link in place - point the antennas as per the map. Now have someone on the ground monitor your connection - you can use winbox interface to monitor your connection, this will enable you to 'point' the antenna. Once you have one done repeat at the other end.

You are going to get interference if all your cards are set to the 5.8ghz band. I'd use the 5.8ghz for the long haul. Use 5.1 and 5.3 for your offices w/the appropiate power levels of course... This will help tremendously with throughput.

4) Routing is the best way to handle this type of setup. If you plan to do any firewalling then don't do it in the radios if you want max throughput. Use a PC based MT router/firewall. Most likely you'll only need one at home base. I use MT based PC routers on my big links (20Mbps+) at the clients location to do all the firewalling/NATing if necessary.

5) If you can get the 32.5 dbi antennas for the long link - that would be best. Less interference, more directed beam.

Thom

3: How the heck I will point the antennas to each other with bare eyes at 35 miles apart

Use a magnetic compass and binoculars - we hit 40km+ links about 95% of the time, first time, with a little tweaking to get the best signal...

Question have some one tryed Green laser to align antennas ?
i will try my 35 mw green laser some night and se if it possible to use that

//Rickard

Check out the WIKI.
There was a presentation at Dallas last year's MUM.
The presenter used a "BIG RED BALOON” to aid in aiming the antennas.

A good "quickie" method of getting a better view of the "far end" of a link.
From this rough alignment, it would make fine adjustment quicker.

Things that make you go Hmmmmm....

Craig

Let's see Climbing on a 200Ft Tower at night which is on top of a 2000Ft Mountain

Ughh I am not a dark rider..

Baloon... nope that won't work either the tower isn't even visible (well there is a LOS if you can see

one side is very easy I am pointing to a single peak of the area in may be 60 miles (MT Diablo, CA) it's like a dude in the girls boarding school but the other side is the tricky one the mountain has a long ridge...

I think I will go with my instinct and set one side up and try to find the signal instead of tower

[/list]

if you have RB with speaker you can try out that buzzer script - that sounds depending on signal strength.

telescope?

it would be usable in other areas of network administration too