Hi,
I just upgraded another link that we have Celeron 1.5ghz boards on each
side... going 2 miles:
20mhz channel = 33.2Mbps one direction
40mhz channel = 56.9Mbps one direction
I have to say I am truly impressed if the number Matt posted below is
correct (and not a typo or something). Gettin
That is what we will do for now. I want to reuse as much spectrum as
possible with as little consumption as possible. Having 4 AP's all
able to TX on the same channel would facilitate that, but if they
expect RX on that channel then its a no go. The end points are far
enough away with high enough g
That is cool Travis - Thanks for that info.
I have been "tip Toeing" around V3.x since it came out and have avoided
downloading it to even try it out. This last batch of RB532's came in with
it preloaded on them is the only reason I have even seen it thus far. I
guess I am a strange puppy and I
Mac,
I have been running in production links and GigE routers since 3.0rc13.
Our main edge router is MT v3.1 right now and is running perfectly. I
have upgraded about 10 of our RB532's with v3.2 and it has been perfect
so far. Some of the new statistics are really cool (like the Potential
Thro
Can't you just "bond" the two wireless cards and get the throughput you
want that way?
Travis
Microserv
Jeromie Reeves wrote:
Sounds good. In the next week or two (depends on weather) I will be
changing my main links. Good to have some numbers to compare against.
I will make a note to post
Travis,
Do you know anyone that has the new MT v3.x in a production environment?
I have two RB532's that were just configured using Nstream and I am looking
at putting them in a work situation. I too am ordering some 333 and RB600's
if I can find some tonight. The RB532's that are ready to
Sounds good. In the next week or two (depends on weather) I will be
changing my main links. Good to have some numbers to compare against.
I will make a note to post my numbers (P4 to RB133). What about signal
levels and mpci cards used? Now if MT would allow different sized
NStream2 setups (say 40/
Hi,
5.3ghz, 3 miles, 5mhz channel, 7.8Mbps one direction
5.3ghz, 3 miles, 40mhz channel, 52.3Mbps one direction
All these tests are with Nstreme on, but no framer policy. I know
people have squeezed more by playing with the framer settings, but we
have never needed to do that.
I'm sure more
What about 5mhz channels? Do you have enough signal to try 40 mhz? I
am about to replace 5 links with MT 5.8. Does more CPU help on the
sending side, say P4 to RB133/333.
On 2/9/08, Travis Johnson <[EMAIL PROTECTED]> wrote:
>
> Here is a real world MT test running RB532's (333mhz) with v3.2 OS:
Here is a real world MT test running RB532's (333mhz) with v3.2 OS:
5.3ghz, 3 miles, 10mhz channel, 18.3Mbps one direction
5.8ghz, 9 miles, 20mhz channel, 27.3Mbps one direction
A more comparable test would be using the new MT RB600 units (as they
are almost exactly the same price as the WAR4
10 matches
Mail list logo
