Why on earth would anyone run unstable routing software in a network pushing
that much traffic?

2011/3/26 Josh Luthman <[email protected]>

> Which RC?
> On Mar 25, 2011 6:04 PM, "Travis Johnson" <[email protected]> wrote:
> > We are running it in production on at least 5 of our main routers
> > (biggest one is moving 800Mbps of traffic).
> >
> > Travis
> > Microserv
> >
> >
> > On 3/25/2011 3:37 PM, Tristram Cheer wrote:
> >> Then your silly or dont really have a big network.
> >>
> >> We run nearly 100 towers with around 1000 clients and wouldn't dream of
> >> putting ROS 5 into production right now, It's simply too buggy and it
> gets
> >> very tiresome every time we report a ROS 4 fault to MT and am told to
> update
> >> to ROS 5.0RCxx
> >>
> >> I'm betting ROS 5.0 isn't stable enough for production use until late
> 11Q2
> >> or early 11Q3
> >>
> >> 2011/3/25 Chupaka<[email protected]>
> >>
> >>> What do you mean? =) We have v5.0rc4 working in production.
> >>>
> >>>
> >>> --
> >>> Подпись:
> >>> (добавляется в конце всех исходящих писем)
> >>>
> >>>
> >>>
> >>> 2011/3/24 Butch Evans<[email protected]>
> >>>
> >>>> On 03/24/2011 01:37 PM, Robert Andrews wrote:
> >>>>
> >>>>> I just can't believe what problems there are with all the 5 betas...
> >>>>> Not one of the release candidates is work a c...p
> >>>>>
> >>>> I can believe it. :-(
> >>>>
> >>>>
> >>>> --
> >>>> ********************************************************************
> >>>> * Butch Evans * Professional Network Consultation*
> >>>> * http://www.butchevans.com/ * Network Engineering *
> >>>> * http://store.wispgear.net/ * Wired or Wireless Networks *
> >>>> * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! *
> >>>> * NOTE THE NEW PHONE NUMBER: 702-537-0979 *
> >>>> ********************************************************************
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Mikrotik mailing list
> >>>> [email protected]
> >>>> http://www.butchevans.com/mailman/listinfo/mikrotik
> >>>>
> >>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
> >>>> RouterOS
> >>>>
> >>> -------------- next part --------------
> >>> An HTML attachment was scrubbed...
> >>> URL:<
> >>>
>
> http://www.butchevans.com/pipermail/mikrotik/attachments/20110325/89868eda/attachment.html
> >>> _______________________________________________
> >>> Mikrotik mailing list
> >>> [email protected]
> >>> http://www.butchevans.com/mailman/listinfo/mikrotik
> >>>
> >>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
> >>> RouterOS
> >>>
> >> -------------- next part --------------
> >> An HTML attachment was scrubbed...
> >> URL:<
>
> http://www.butchevans.com/pipermail/mikrotik/attachments/20110326/eb871f2b/attachment.html
> >
> >> _______________________________________________
> >> Mikrotik mailing list
> >> [email protected]
> >> http://www.butchevans.com/mailman/listinfo/mikrotik
> >>
> >> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
> RouterOS
> > _______________________________________________
> > Mikrotik mailing list
> > [email protected]
> > http://www.butchevans.com/mailman/listinfo/mikrotik
> >
> > Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
> RouterOS
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://www.butchevans.com/pipermail/mikrotik/attachments/20110325/f9093d64/attachment.html
> >
> _______________________________________________
> Mikrotik mailing list
> [email protected]
> http://www.butchevans.com/mailman/listinfo/mikrotik
>
> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
> RouterOS
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://www.butchevans.com/pipermail/mikrotik/attachments/20110326/5e1a3894/attachment.html>
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS

Reply via email to