This really comes down to preference and "budget" . I would agree that the 532 (non production as well) is a small board, however, starting up, 50-100 customers, this box will work. Its an industrial board that has proven itself quite capable. It really comes down to the amount of traffic etc. I have customers running a 532 board with 8 meg connections, with over 100 queues on it. It was doing NAT as well. This board never went about 50-60% .
If that will handle your traffic, then great, but keep in mind, when you have 200 customers and moving 20 meg of traffic, it might not be enough! And most liekly will not be enough! I love how people want to use OLD servers, and old PCs as Mikrotiks. Ya, cheap cheap, fun fun, but they already have years of use on them! Just makes me wonder about some people! An example was a customer of ours, the owner starting complaining about Mikrotik how unstable it was. Start taking to him a bit, and he told me what kind of PC it was on. After a bit more talking i asked where the PC was from. He said when his windows 98 desktop was running too slowly, he decided to put another NIC it in and bingo, instant Mikrotik. But it was always failing due to power supply, hard drive etc. Of course, they also placed in the $15 power supplies back into it! Regardless on what you use, industrial hardware is the way to go! The 433AHs are very capable as well, much faster than the 532s, as well as the 1000 board. ------------------------------ * Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer Link Technologies, Inc -- Mikrotik & WISP Support Services* 314-735-0270 http://www.linktechs.net <http://www.linktechs.net/> */ Link Technologies, Inc is offering LIVE Mikrotik On-Line Training <http://www.linktechs.net/onlinetraining.asp>/* Tom DeReggi wrote: > I'm not against Mikrotik Software as a core router. > > I am however against a MT532 as a core router. > A MT532 is fine as an AP or SU, that manages the subs on it, but for the > core of a WISP, one needs more headroom. > We don't use anything less than a Quad Proc now a days, but then again, we > need to support multi port GB. > > But even at low speeds, processor headroom is important. Its important to > have the headroom when you need it. > It cost so little, for the extra processing power. There becomes huge > differences in throughput based on packet size. > When things get ugly are when you get a DOS attack that has either small > packets 64bytes, or doesn't wait for acks to keep sending. > Its also important to have enough processing for initiating testing > routines, from the device. Or to handle logging, during diagnostic periods. > > There may very well be performance benefits of non-intel SBCs that handle > interupts differently than x86, but still don't trust your core on a $150 > SBC. > There is to much revenue at risk. > > My understandign is MT now has some faster proc rack systems such as their > 1000series? Maybe those are better options? > > Just my opinion. > > Tom DeReggi > RapidDSL & Wireless, Inc > IntAirNet- Fixed Wireless Broadband > > > ----- Original Message ----- > From: "Dennis Burgess" <[EMAIL PROTECTED]> > To: "WISPA General List" <wireless@wispa.org> > Sent: Wednesday, July 09, 2008 3:12 PM > Subject: Re: [WISPA] Suggestions for Mikrotik Bandwidth Management > > > >> It is a great solution. Many ISPs use Mikrotik to do everything, and >> bandwidth management is one of those! Its a great Permanent solution! >> If you don't like the 532 as a core router, check into a PowerRouter 732! >> >> ------------------------------ >> * Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer >> Link Technologies, Inc -- Mikrotik & WISP Support Services* >> 314-735-0270 >> http://www.linktechs.net <http://www.linktechs.net/> >> >> */ Link Technologies, Inc is offering LIVE Mikrotik On-Line Training >> <http://www.linktechs.net/onlinetraining.asp>/* >> >> >> >> Patrick Nix Jr. wrote: >> >>> Right, but for now we don't have the imagestream all I have that will >>> easily config is the MT I realize this probably isn't a good permanent >>> solution, I just need something to get by for a month or two >>> >>> __________________________________________ >>> >>> Patrick Nix, Jr., >>> csweb.net >>> (918) 235-0414 >>> http://www.csweb.net >>> E-Mail: [EMAIL PROTECTED] >>> >>> ==================================================================== >>> ATTENTION: This e-mail may contain information that is confidential in >>> nature. If you are not the intended recipient, please delete this e-mail >>> and notify the sender immediately. Thank you. >>> ==================================================================== >>> >>> >>> -----Original Message----- >>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >>> Behalf Of Bo Ring >>> Sent: Wednesday, July 09, 2008 3:02 PM >>> To: WISPA General List >>> Subject: Re: [WISPA] Suggestions for Mikrotik Bandwidth Management >>> >>> You can use the Imagestream solo to do this and then not replace >>> anything. It can do packet based bandwidth management with PowerNoc/ >>> PowerCode. >>> >>> On Jul 9, 2008, at 2:12 PM, Patrick Nix Jr. wrote: >>> >>> >>> >>>> Is there anyone using MT for bandwidth management? We are waiting on >>>> our PowerNOC/ Imagestream solution but I need something to get us by >>>> until then >>>> >>>> What are some suggested settings and what kind of toll is it on CPU >>>> resources RB532 >>>> >>>> >>>> >>>> >>>> >>>> Thanks >>>> >>>> >>>> >>>> __________________________________________ >>>> >>>> >>>> >>>> Patrick Nix, Jr., >>>> >>>> csweb.net >>>> >>>> (918) 235-0414 >>>> >>>> http://www.csweb.net <http://www.csweb.net/> >>>> >>>> E-Mail: [EMAIL PROTECTED] >>>> >>>> >>>> >>>> ==================================================================== >>>> >>>> ATTENTION: This e-mail may contain information that is confidential in >>>> >>>> >>> >>>> nature. If you are not the intended recipient, please delete this e- >>>> mail and notify the sender immediately. Thank you. >>>> >>>> ==================================================================== >>>> >>>> >>>> >>>> >>>> >>>> ---------------------------------------------------------------------- >>>> ---------- >>>> WISPA Wants You! Join today! >>>> http://signup.wispa.org/ >>>> ---------------------------------------------------------------------- >>>> ---------- >>>> >>>> WISPA Wireless List: wireless@wispa.org >>>> >>>> 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: wireless@wispa.org >>> >>> 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: wireless@wispa.org >> >> 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: wireless@wispa.org > > 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: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
