Good point. I see the same. -Ty
On Wed, Feb 5, 2014 at 11:35 AM, Craig Baird <[email protected]> wrote: > I have several tower sites where I'm bridging APs. I'm graphing the > individual interfaces in the bridge using Cacti. Looking at the graphs, > they all look very different. If it were truly acting like a hub, I think > you'd see practically the same graph on every interface. > > Craig > > > Quoting Ty Featherling <[email protected]>: > > When I implemented the "port isolation" rule I posted earlier. I logged >> the >> traffic first to make sure I was not blocking anything I didn't intend. >> The >> only traffic I saw was broadcast based; EGMP, UBNT Discovery, CDP, etc. >> This doesn't rule out the switching function of a bridge since this >> traffic >> isn't destined for a known host MAC. It doesn't prove it either because >> there probably wasn't any real port-to-port host-to-host traffic on that >> router at that time. >> >> I would love to know that a bridge is the same as a hardware switch but >> just in software and thus manageable by ROS. >> >> -Ty >> >> >> On Wed, Feb 5, 2014 at 11:04 AM, Bill Prince < >> [email protected]> wrote: >> >> Google is your friend. Searched the MT forum archives and found this >>> thread posted in November 2012: >>> >>> http://forum.mikrotik.com/viewtopic.php?f=3&t=67492 >>> >>> >>> Bottom line from Janisk is as follows: >>> >>> /to clear some misconceptions if you talk about RouterOS and >>> RouterBOARD then difference between bridging and switching is as >>> follows:// >>> // >>> //bridge interface is software implementation of hardware switch and >>> thus, features can be extended using software. Basic functionality >>> is directly comparable to switching. Performance depends on speed >>> and capabilities of the CPU// >>> // >>> //Switching is done in hardware by special chip that has certain >>> limitations as all the possible features are predetermined by >>> hardware switch and what configuration possibilities are and can >>> made available via controlling interface. Since switching is not >>> done by RouterOS then packets switched by hardware are not visible >>> by RouterOS, hence no control over those./ >>> >>> >>> >>> >>> bp >>> >>> >>> On 2/5/2014 8:39 AM, Stephen Wong wrote: >>> >>> I swear, if there is proved evidence that a Mikrotik RouterOS 5 works >>>> like >>>> a hub with the bridge ports configured in software (and with the >>>> hardware >>>> switch chip also working like a hub), I dump immediately all Mikrotik >>>> equipments in our personal / business environment. If it is the case, >>>> it's >>>> just such a big crap that worth nothing in network field. >>>> >>>> Please, give me the evidence, and I'll go back to Cisco / Juniper >>>> without >>>> regret. >>>> >>>> Stephen WONG >>>> >>>> >>>> On Thu, Feb 6, 2014 at 12:28 AM, <[email protected] >>>> >wrote: >>>> >>>> Message: 4 >>>> >>>>> Date: Wed, 05 Feb 2014 08:26:18 -0800 >>>>> From: Bill Prince <[email protected]> >>>>> Subject: Re: [Mikrotik] Bridge Ports showing with an S on version 6.7 >>>>> To: [email protected] >>>>> Message-ID: <[email protected]> >>>>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed >>>>> >>>>> The software bridge used to operate like a hub, and according to some >>>>> reports that we've gotten, the switch chip also operated like a hub. >>>>> >>>>> However, I have heard through the rumor mill that the hub-like >>>>> operation >>>>> of the switch chip was fixed in ROS 6.x. >>>>> >>>>> I have not personally tested either one. >>>>> >>>>> This would be a good point for someone that actually knows to chime in. >>>>> >>>>> Chupaka? >>>>> >>>>> Butch? >>>>> >>>>> >>>>> bp >>>>> >>>>> >>>>> -------------- next part -------------- >>>>> >>>> An HTML attachment was scrubbed... >>>> URL: <http://mail.butchevans.com/pipermail/mikrotik/ >>>> attachments/20140206/324bf0df/attachment.html> >>>> _______________________________________________ >>>> Mikrotik mailing list >>>> [email protected] >>>> http://mail.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://mail.butchevans.com/pipermail/mikrotik/ >>> attachments/20140205/23fe62be/attachment.html> >>> >>> _______________________________________________ >>> Mikrotik mailing list >>> [email protected] >>> http://mail.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://mail.butchevans.com/pipermail/mikrotik/ >> attachments/20140205/b352013b/attachment.html> >> >> _______________________________________________ >> Mikrotik mailing list >> [email protected] >> http://mail.butchevans.com/mailman/listinfo/mikrotik >> >> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >> RouterOS >> >> >> > > > _______________________________________________ > Mikrotik mailing list > [email protected] > http://mail.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://mail.butchevans.com/pipermail/mikrotik/attachments/20140205/db8aee5d/attachment.html> _______________________________________________ Mikrotik mailing list [email protected] http://mail.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
