Let's take a look at the SR2. It was poorly designed to have a rf switch chip that changed between u.fl and mmcx connectors without any type of surge suppression. This caused the switch chip to get burned out due to minimal ESD issues. The XR2 was released and that component was removed and a grounding strap was included with every card. Did they learn from their mistake and improve upon it? Yes. Kuddos! But to say that it was without issues is incorrect. I've had NSM2's lock up, they connect to the AP, get stuck at a 1/6 data rate and kill the performance of an AP. Only thing that fixes it was to kick the client NSM2 and reboot the device (if you didn't reboot, it would recur in about 6 hours or so). Was this fixed in firmware ? Yes. Again, Kuddos!
I would bet that you do have lock-ups, but don't notice them as an issue. Most of our customers power-cycle everything before calling in as standard procedure. That lockup could be unnoticed if that is the case. It's not that we're against you Matt, it's just that your statements begin to lack credibility when they include "I've never had one lock up in 2 years". I've been using UBNT devices for the past 6 years and can tell you that if your case is really true, you are one lucky SOB! Regards, Chuck On Fri, Sep 14, 2012 at 1:51 PM, Matt Hoppes <mhop...@indigowireless.com>wrote: > Can you give some examples where you've had equipment lock up? We have > many units deployed in the field, on towers, customer sites. The only > time I've ever had a lockup was with the 5.3.x bug where after 30 days > of uptime a change would cause a lockup. > > I've never had anything lock up by itself. We even go so far as to tell > our customers, if you ever have to power cycle your radio or (us > supplied) router, call us because something is wrong. > > To date (two years) I've received 0 calls regarding this. > > > Matt Hoppes > Director of Information Technology > Indigo Wireless > +1 (570) 723-7312 > > On 9/14/12 1:29 PM, Doug Clark wrote: > > Matt, Have to disagree with you here. UBNT equipment does not just > > run...... > > It locks up for no reason and requires a power cycle in order to come > back. > > If you want equipment that " JUST RUNS " and requires no baby sitting > > that equipment has a Cambium logo on it. > > You pay dearly for it and I have a significant amount in my network but > > I am not deploying it because the cost is too high and > > the bandwidth is too low. UBNT equipment is very high maintainance and > > super hard to diagnosis what the problem is when you have one. > > With all that being said I am still currently only deploying UBNT and > > actually taking down Canopy FSK to replace it with UBNT 2X2 > > ~Doug > > /-------Original Message-------/ > > /*From:*/ Matt Hoppes <mailto:mhop...@indigowireless.com> > > /*Date:*/ 9/14/2012 9:42:32 AM > > /*To:*/ WISPA General List <mailto:wireless@wispa.org> > > /*Subject:*/ Re: [WISPA] Ubiquiti next product.... another router? > > Greg, > > I don't ever recall seeing bleeding-edge firmware with bugs released > > from Ubiquiti.... unless you mean the betas? But that's what they > > are... betas. Since 5.3.3 up to the current 5.5.2 release I haven't > > had any problems with the final releases of software. > > I can't count the number of Linksys, DLink, Hawking, whatever wireless > > routers we've replaced for customers because they had problems with > > their Internet. We put in a Power AP-N, or an AirRouter and we never > > hear from them again. > > Truth be told... Ubiquiti equipment just runs... it doesn't need > > rebooted. It doesn't need babysat. It just runs. > > No I am not being paid to make these statements. I just have many years > > working in IT. I've used Cisco, MikroTik, Alvarion, Motorola and now > > Ubiquiti. The Ubiquiti equipment just works. I have a backhaul that's > > been up for over a year with no reboots.... and no problems. > > Matt Hoppes > > Director of Information Technology > > Indigo Wireless > > +1 (570) 723-7312 > > On 9/14/12 11:20 AM, Greg Ihnen wrote: > > > Are people going to be able to tolerate the bleeding-edge cycle of > > > bugs/firmware updates that has been the history with their wireless > gear? > > > > > > Once again they're breaking new ground, this time with low cost/high > pps > > > throughput. Will they be able to make it powerful (rich feature set) > > > /and/ easy? > > > > > > It's going to have to be really good to make people switch. > > > > > > Maybe they're going for a niche market of people who want only > features > > > relevant to the WISP market (bandwidth management, bandwidth > accounting > > > etc, vlans) and not people who want a do-all box like MT which has a > lot > > > of features most WISPs probably don't use (BGP and the forwarding > > > protocols come to mind). > > > > > > Greg > > > > > > On Fri, Sep 14, 2012 at 11:11 AM, Paolo Di Francesco > > > <paolo.difrance...@level7.it <mailto:paolo.difrance...@level7.it> > > <mailto:paolo.difrance...@level7.it>> wrote: > > > > > > Hi all > > > > > > I see that Ubiquiti is launching a new product, a router. > > > > > > Well, personally, I do not think that it's a good idea, hard > > market and > > > I really do not see a real reason why I should buy the Ubiquiti > > router > > > instead of other well knows products > > > > > > From my perspective the value or a core/edge router is not only > > in the > > > number of packets, it's more into the number of bugs and > > instabilities. > > > > > > A new product has less or more bugs/instabilities than others > working > > > since years in my network? > > > > > > I am not sure that I want to restart thinking new workarounds for > > a new > > > brand. > > > > > > Comments? > > > > > > > > > -- > > > > > > > > > Ing. Paolo Di Francesco > > > > > > Level7 s.r.l. unipersonale > > > > > > Sede operativa: Largo Montalto, 5 - 90144 Palermo > > > > > > C.F. e P.IVA 05940050825 > > > Fax : +39-091-8772072 <tel:%2B39-091-8772072> > > > assistenza: (+39) 091-8776432 <tel:%28%2B39%29%20091-8776432> > > > web: http://www.level7.it > > > > > > > > > > > > _______________________________________________ > > > Wireless mailing list > > > Wireless@wispa.org <mailto:Wireless@wispa.org> > > <mailto:Wireless@wispa.org> > > > http://lists.wispa.org/mailman/listinfo/wireless > > > > > > > > > > > > > > > _______________________________________________ > > > Wireless mailing list > > > Wireless@wispa.org <mailto:Wireless@wispa.org> > > > http://lists.wispa.org/mailman/listinfo/wireless > > > > > _______________________________________________ > > Wireless mailing list > > Wireless@wispa.org <mailto:Wireless@wispa.org> > > http://lists.wispa.org/mailman/listinfo/wireless > > > > > > > > > > _______________________________________________ > > Wireless mailing list > > Wireless@wispa.org > > http://lists.wispa.org/mailman/listinfo/wireless > > > _______________________________________________ > Wireless mailing list > Wireless@wispa.org > http://lists.wispa.org/mailman/listinfo/wireless >
_______________________________________________ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
