I think what they are saying is if you are not currently setup for vlans per ap, then it probably doesn't make sense, just adds more complexity. I see your point to separate traffic down to the Mikrotik so you can torch local traffic to AP.
So you would have something like this Mikrotik (Customer Bridge where DHCP server resides) bridged to vlan which is then tagged through to untagged port on R6? This would allow you to monitor ap traffic on a per vlan basis on the MIkrotik. Now I feel confused LOL.... Erich Kaiser North Central Tower er...@northcentraltower.com Office: 630-621-4804 Cell: 630-777-9291 On Tue, Jun 28, 2016 at 10:52 AM, Nate Burke <n...@blastcomm.com> wrote: > Ok, so I'm hearing "the way you're doing it is wrong" Is there a better > way? Or just let the R6 act as a dumb switch, and then log into that to > try to troubleshoot any per port issues. > > On 6/28/2016 10:49 AM, Josh Reynolds wrote: > > I think you have a fundamental misunderstanding of the purpose of vlans... > On Jun 28, 2016 10:48 AM, "Nate Burke" <n...@blastcomm.com> wrote: > >> Then how do I get all the Ports on the Edgepoint to share the same IP >> Space? >> >> On 6/28/2016 10:45 AM, Mike Hammett wrote: >> >> *nods* just leave the VLANs as native interfaces on the Mikrotik. No need >> to bridge them. >> >> >> >> ----- >> Mike Hammett >> Intelligent Computing Solutions <http://www.ics-il.com/> >> <https://www.facebook.com/ICSIL> >> <https://plus.google.com/+IntelligentComputingSolutionsDeKalb> >> <https://www.linkedin.com/company/intelligent-computing-solutions> >> <https://twitter.com/ICSIL> >> Midwest Internet Exchange <http://www.midwest-ix.com/> >> <https://www.facebook.com/mdwestix> >> <https://www.linkedin.com/company/midwest-internet-exchange> >> <https://twitter.com/mdwestix> >> The Brothers WISP <http://www.thebrotherswisp.com/> >> <https://www.facebook.com/thebrotherswisp> >> >> >> <https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg> >> ------------------------------ >> *From: *"Josh Reynolds" <j...@kyneticwifi.com> <j...@kyneticwifi.com> >> *To: *af@afmug.com >> *Sent: *Tuesday, June 28, 2016 10:44:28 AM >> *Subject: *Re: [AFMUG] Mikrotik Bridging VLans >> >> It doesn't like that you're bridging all these vlans. From experience, >> it's nothing but broken-ness. >> >> You can still torch each vlan interface you know. >> On Jun 28, 2016 10:42 AM, "Nate Burke" <n...@blastcomm.com> wrote: >> >>> I'm working on the bench with a UBNT Edgepoint (R6 model) The newest >>> firmware allows you to set per port untagged Vlans in switch mode. I'm >>> thinking of using this to power a cluster of AP's, but I'd like to keep the >>> ability to view per port traffic in the mikrotik via Torch for >>> monitoring/troubleshooting purposes. My Plan was to put each port on the >>> R6 on a different Vlan, Have a Trunk port to the mikrotik, then just bridge >>> the Vlans together in the Mikrotik. This mostly works, as the Mikrotik can >>> talk to each AP, but the AP's cannot ping each other, and it seems that I >>> have random packet loss from the Mikrotik to the AP's. Is there a setting >>> I'm missing that's blocking the traffic between Vlans, or is this a >>> Edgepoint problem? Or does it not like that I'm bridging all these Vlans >>> that are on the same Mikrotik interface. >>> >> >> >> >
