Travis,
This was my main reason for being such a critical opponent to your
request for Mikrotik support. We fought with Mikrotik over a year to
get them to fix the issues and it never happened. We finally stopped
about a year ago and went back to Canopy and Alvarion. (More Canopy
lately with the 400 series)
I can't tell you the number of supouts we sent or the number of tests
we ran. We'd be up in the middle of the night, reconfiguring every
CPE with different settings and then changing the APs based on their
recommendations. Basically, we were doing their field testing for
them and to no avail. Nothing they recommended fixed things. They
finally said that we didn't have enough horsepower at the AP. So, we
bought super powerful PCs for APs. Again, no help. Now they have
their own super powerful hardware and it still hasn't fixed the
issue.
So, for the savings of money on equipment, we invested a lot in R & D
for both time and dollars. (I have tons of dead equipment sitting
here that didn't work.)
So, when adding up all the hours debugging for Mikrotik (with no
results) and the extra equipment we had to buy to make things work,
we bailed. Canopy and Alvarion are cheaper in the long run and we
sleep more.
We use Mikrotik for a lot of our routers and most of the fights we
have fought there have been won. (BGP and OSPF) However, wireless
never got better. (For PtMP)
As far as support, Alvarion has been fantastic and thrown many
resources our way. Although, we haven't needed them lately. Canopy
has a large base with lots of third party options and community
support. When problems with Canopy have come up, we do see them
working on resolving them and software upgrades reflect that.
I think Mikrotik's place for us has been reduced to mostly local
repeaters.
I have many (over 40) MT AP's with SR5 cards on the AP side and Compex
WLM54SAG cards on the client side, with RB411's as well. All my clients
are the same, and running MT, and they all do the same thing. :(<br>
<br>
Once again, MT is aware of the problem, but rather than fix it, they
decide to work on 802.11n support. Who do they think is going to buy
more product with 802.11n support when their current product doesn't
even work?<br>
<br>
Travis<br>
Microserv<br>
<br>
Kurt Fankhauser wrote:
<blockquote cite="" class="moz-txt-link-rfc2396E" href="mailto:mid:[EMAIL PROTECTED]">"mid:[EMAIL PROTECTED]"
type="cite">
<pre wrap="">Butch,
Nope, I am using the senao NMP-8602+ card on all these AP's. From what I
can
tell this problem shows its face when you have a mixed CPE's consisting of
PRISM/Atheros chipsets.
Can I solve this problem by removeing all the PRISM clients???? At this
point I am willing to invest in replacing our old CB3/CPE-200 stuff
anyways
as it only makes up 10% of my network.
Kurt Fankhauser
WAVELINC
P.O. Box 126
Bucyrus, OH 44820
419-562-6405
<a class="moz-txt-link-abbreviated"
href="" class="moz-txt-link-rfc2396E" href="http://www.wavelinc.com">"http://www.wavelinc.com">www.wavelinc.com</a>
-----Original Message-----
From: <a class="moz-txt-link-abbreviated"
href="" class="moz-txt-link-rfc2396E" href="mailto:[EMAIL PROTECTED]">"mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a>
[<a class="moz-txt-link-freetext"
href="" class="moz-txt-link-rfc2396E" href="mailto:[EMAIL PROTECTED]">"mailto:[EMAIL PROTECTED]">mailto:[EMAIL PROTECTED]</a>]
On
Behalf Of Butch Evans
Sent: Tuesday, August 26, 2008 3:16 PM
To: WISPA General List
Subject: Re: [WISPA] MT interface randomly dumping clients.
On Mon, 25 Aug 2008, Kurt Fankhauser wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Has anyone else seen this problem I am seeing. On my
Mikrotik sites
with Atheros AP's the interface will decide to completely dump all
of the atheros clients and then they reconnect again within 2
seconds. You can tell this happens because the uptimes are so
short. But the prism clients they never get dumped and their
uptimes are accurate since they were last power cycled. Take a look
at this screen shot you can see the problem clearly. This is
happening on ALL of my towers that have Mikrotik AP's.
</pre>
</blockquote>
<pre wrap=""><!---->
Let me guess...you are using the XR2 or XR5? This is a known issue
that is especially bad with Tranzeo client radios and XR2 at the AP.
As someone else mentioned, there is a lot of finger pointing going
on relating to this issue. From what I can tell, this issue does
not have a negative impact on Mikrotik CPE (or most other CPEs for
that matter).
</pre>
</blockquote>
</body>
</html>
--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
WISPA Wireless List: [email protected]
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
WISPA Wireless List: [email protected]
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
