Interesting. Let us know! Hope you have a great weekend! On Fri, Nov 2, 2018 at 1:35 PM Josh Luthman via Mikrotik-users < mikrotik-users@wispa.org> wrote:
> Small update to this. Updating the bh didn't resolve the issue - still > needed to "restart" OSPF (specifically I'd disable & enable the OSPF > network). > > Yesterday I turned off Multicast Enhancement on both masters of the BH. I > just hit 24 hour adjacency which I think is a new record. Time will tell... > > > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > On Wed, Oct 31, 2018 at 1:12 PM, Josh Luthman <j...@imaginenetworksllc.com > > wrote: > >> In my mind nothing but multicast. I don't need any more nightmares >> tonight. Halloween and all that ;) >> >> Josh Luthman >> Office: 937-552-2340 >> Direct: 937-552-2343 >> 1100 Wayne St >> Suite 1337 >> Troy, OH 45373 >> >> On Wed, Oct 31, 2018, 1:09 PM Robert Andrews via Mikrotik-users < >> mikrotik-users@wispa.org wrote: >> >>> Makes you wonder what other corners of the IP protocol are being >>> squashed by our radio coms... >>> >>> On 10/31/2018 08:34 AM, Josh Luthman wrote: >>> > Well it's all AirOS and it's supposed to all act the same way from my >>> > batch update scripts. >>> > >>> > No, I don't waste time with AirControl 1, 2, or 1 again... >>> > >>> > >>> > Josh Luthman >>> > Office: 937-552-2340 >>> > Direct: 937-552-2343 >>> > 1100 Wayne St >>> > Suite 1337 >>> > Troy, OH 45373 >>> > >>> > On Wed, Oct 31, 2018 at 11:23 AM, Robert via Mikrotik-users >>> > <mikrotik-users@wispa.org <mailto:mikrotik-users@wispa.org>> wrote: >>> > >>> > When you mentioned 3 Ghz radios, I wondered about that as I have >>> some 3 >>> > ghz equip that was archaic versions... >>> > >>> > On 10/31/18 7:03 AM, Josh Luthman via Mikrotik-users wrote: >>> > > So...uhh...this is kind of embarrassing. I may have fixed it >>> (OSPF just >>> > > his adjacency of 19h, previous max uptime was 12 hours). >>> Someone >>> > > mentioned the Ubnt backhaul versions or something so I double >>> checked >>> > > and it never got updated. One of the two backhauls was running >>> 5.5 or >>> > > something ancient. I upgraded it and everything seems to be OK >>> now, at >>> > > least we're hitting a new record after 4 days of <12 hour >>> uptimes. >>> > > >>> > > I don't work much with multicast but I was always under the >>> impression >>> > > that APWDS and STAWDS simply acted as a transparent bridge. >>> Clearly it >>> > > doesn't. >>> > > >>> > > Sorry for the noise and thanks for the sanity checks/making me >>> look at >>> > > the firmware versions on the backhauls! >>> > > >>> > > >>> > > Josh Luthman >>> > > Office: 937-552-2340 >>> > > Direct: 937-552-2343 >>> > > 1100 Wayne St >>> > > Suite 1337 >>> > > Troy, OH 45373 >>> > > >>> > > On Tue, Oct 30, 2018 at 4:15 PM, Jesse Dupont via Mikrotik-users >>> > > <mikrotik-users@wispa.org <mailto:mikrotik-users@wispa.org> >>> > <mailto:mikrotik-users@wispa.org <mailto:mikrotik-users@wispa.org >>> >>> >>> > wrote: >>> > > >>> > > I would make sure spanning tree is off on the 750 sw bridge >>> and go >>> > > ahead and turn off Multicast Enhancement on the APs (leave >>> Multicast >>> > > Allowed as enabled). >>> > > >>> > > Sent from my iPhone >>> > > >>> > > On Oct 30, 2018, at 12:52 PM, Josh Luthman >>> > > <j...@imaginenetworksllc.com >>> > <mailto:j...@imaginenetworksllc.com> >>> > <mailto:j...@imaginenetworksllc.com >>> > <mailto:j...@imaginenetworksllc.com>>> >>> > > wrote: >>> > > >>> > >> Multicast Data is allowed and Multicast Enhancement is >>> Enabled on >>> > >> the AP. The STA Multicast Data is allowed by there is no >>> option >>> > >> for Multicast Enhancement. Should I disable the >>> enhancement on >>> > >> the AP only? I assume I have to enable Multicast on these >>> links. >>> > >> (FYI one is 5 GHz the other is 3.65 GHz - 802.11n "M" gear). >>> > >> >>> > >> There is an RB750 switch (software bridge). L2 MTU 1598. >>> > >> >>> > >> >>> > >> Josh Luthman >>> > >> Office: 937-552-2340 >>> > >> Direct: 937-552-2343 >>> > >> 1100 Wayne St >>> > >> Suite 1337 >>> > >> Troy, OH 45373 >>> > >> >>> > >> On Tue, Oct 30, 2018 at 2:31 PM, Jesse Dupont via >>> Mikrotik-users >>> > >> <mikrotik-users@wispa.org <mailto:mikrotik-users@wispa.org> >>> > <mailto:mikrotik-users@wispa.org <mailto:mikrotik-users@wispa.org >>> >>> >>> > wrote: >>> > >> >>> > >> I think it’s an LSA flooding issue, especially since it >>> works >>> > >> for a while then stops, then comes back. Disabling the >>> > >> instance as you do to fix it makes the whole adjacency >>> start >>> > >> over which starts with new LSAs. >>> > >> Using a “broadcast” network type doesn’t use broadcasts >>> to >>> > >> establish the adjacencies, it still uses multicast. It >>> just >>> > >> allows for the election of the DR/BDR and more than two >>> > >> endpoints compared to Point-to-point network type. >>> Anyway, >>> > >> it’s not the issue. >>> > >> Have you tried disabling (or enabling if it’s currently >>> > >> disabled) Multicast Enhancement on the two UBNT links? >>> Is >>> > >> there a switch between the two UBNT links in the middle? >>> > >> >>> > >> Sent from my iPhone >>> > >> >>> > >> On Oct 30, 2018, at 11:50 AM, Josh Luthman via >>> Mikrotik-users >>> > >> <mikrotik-users@wispa.org >>> > <mailto:mikrotik-users@wispa.org> <mailto:mikrotik-users@wispa.org >>> > <mailto:mikrotik-users@wispa.org>>> >>> > >> wrote: >>> > >> >>> > >>> In your case did you use a "hidden non used" /30 to >>> build the >>> > >>> eoip and then put your good IPs on top of the eoip? >>> > >>> >>> > >>> >>> > >>> Josh Luthman >>> > >>> Office: 937-552-2340 >>> > >>> Direct: 937-552-2343 >>> > >>> 1100 Wayne St >>> > >>> Suite 1337 >>> > >>> Troy, OH 45373 >>> > >>> >>> > >>> On Tue, Oct 30, 2018 at 1:43 PM, Adam R Johnson >>> > >>> <ajohn...@thewisp.net <mailto:ajohn...@thewisp.net> >>> > <mailto:ajohn...@thewisp.net <mailto:ajohn...@thewisp.net>>> >>> wrote: >>> > >>> >>> > >>> Ours was/is a /29. >>> > >>> >>> > >>> >>> > >>> >>> > >>> *ADAM JOHNSON — PRESIDENT* >>> > >>> (815) 304-6008 | ajohn...@thewisp.net <mailto: >>> ajohn...@thewisp.net> >>> > >>> <mailto:ajohn...@thewisp.net <mailto: >>> ajohn...@thewisp.net>> >>> > >>> PO BOX 460 TAMPICO,IL 61283 >>> > >>> *WWW.THEWISP.NET <http://WWW.THEWISP.NET> | * >>> > >>> <http://www.thewisp.net/>< >>> http://www.facebook.com/thewispnet >>> > <http://www.facebook.com/thewispnet>> >>> > >>> <http://www.twitter.com/thewispnet < >>> http://www.twitter.com/thewispnet>> >>> > >>> >>> > >>> >>> > >>> >>> > >>> On Tue, Oct 30, 2018 at 10:36 AM Josh Luthman via >>> > >>> Mikrotik-users <mikrotik-users@wispa.org <mailto: >>> mikrotik-users@wispa.org> >>> > >>> <mailto:mikrotik-users@wispa.org <mailto: >>> mikrotik-users@wispa.org>>> wrote: >>> > >>> >>> > >>> Between the two routers it's a /30 >>> > >>> >>> > >>> Interesting thing to note...it came back up on >>> its >>> > >>> own over lunch. About 11 hours of it not >>> working >>> > >>> (see the log previously posted). >>> > >>> >>> > >>> >>> > >>> Josh Luthman >>> > >>> Office: 937-552-2340 >>> > >>> Direct: 937-552-2343 >>> > >>> 1100 Wayne St >>> > >>> < >>> https://maps.google.com/?q=1100+Wayne+St+Suite+1337+Troy,+OH+45373&entry=gmail&source=g >>> > < >>> https://maps.google.com/?q=1100+Wayne+St+Suite+1337+Troy,+OH+45373&entry=gmail&source=g >>> >> >>> > >>> Suite 1337 >>> > >>> < >>> https://maps.google.com/?q=1100+Wayne+St+Suite+1337+Troy,+OH+45373&entry=gmail&source=g >>> > < >>> https://maps.google.com/?q=1100+Wayne+St+Suite+1337+Troy,+OH+45373&entry=gmail&source=g >>> >> >>> > >>> Troy, OH 45373 >>> > >>> < >>> https://maps.google.com/?q=1100+Wayne+St+Suite+1337+Troy,+OH+45373&entry=gmail&source=g >>> > < >>> https://maps.google.com/?q=1100+Wayne+St+Suite+1337+Troy,+OH+45373&entry=gmail&source=g >>> >> >>> > >>> >>> > >>> On Tue, Oct 30, 2018 at 1:27 PM, Robert >>> Andrews via >>> > >>> Mikrotik-users <mikrotik-users@wispa.org >>> <mailto:mikrotik-users@wispa.org> >>> > >>> <mailto:mikrotik-users@wispa.org >>> > <mailto:mikrotik-users@wispa.org>>> wrote: >>> > >>> >>> > >>> So this brings up a question that we ran >>> into, >>> > >>> what are the netmasks >>> > >>> around these links? >>> > >>> >>> > >>> On 10/30/2018 10:14 AM, Adam R Johnson via >>> > >>> Mikrotik-users wrote: >>> > >>> > Hey Josh, >>> > >>> > >>> > >>> > Just throwing in my 2 cents here. We >>> have >>> > a very similar situation. What >>> > >>> > was once a powercode bmu, is now a >>> rb3011 >>> > connected to an AF24<>AF24 >>> > >>> > then another rb3011. The 3011s will not >>> > complete adjacency, where the >>> > >>> > bmu and 3011 did originally. Our OSPF >>> > setup is PtP in these scenarios. >>> > >>> > We have this setup in 2 separate >>> > locations on our network, and each has >>> > >>> > the same problem. Our 'stab in the dark' >>> > fix was adding a secondary and >>> > >>> > temporary 192.168.x.x/24 on the segment, >>> > and it created adjacency and >>> > >>> > ran without error. We did the same for >>> > the second instance with the same >>> > >>> > result. >>> > >>> > >>> > >>> > We revisited the issue, to try to >>> resolve >>> > a week or so later, but was >>> > >>> > unable to find the cause or solution in >>> > the time we had. Given that it >>> > >>> > was working without error, albeit >>> > slightly messy, we have left it in >>> > >>> > place with more important things to >>> > tackle. It has been like this for >>> > >>> > about 8 months now. >>> > >>> > >>> > >>> > Im not necessarily advocating this as a >>> > fix, but it is a workaround that >>> > >>> > may provide further information to lead >>> > to the issues cause, and imho is >>> > >>> > a bit nicer than an EoIP tunnel. >>> > >>> > >>> > >>> > Cheers! >>> > >>> > >>> > >>> > *ADAM JOHNSON — PRESIDENT* >>> > >>> > (815) 304-6008 | ajohn...@thewisp.net >>> > <mailto:ajohn...@thewisp.net> >>> > >>> <mailto:ajohn...@thewisp.net >>> > <mailto:ajohn...@thewisp.net>> >>> > >>> <mailto:ajohn...@thewisp.net >>> > <mailto:ajohn...@thewisp.net> >>> > >>> <mailto:ajohn...@thewisp.net <mailto: >>> ajohn...@thewisp.net>>> >>> > >>> > PO BOX 460 TAMPICO,IL 61283 >>> > >>> >>> > < >>> https://maps.google.com/?q=460+TAMPICO,IL+61283&entry=gmail&source=g < >>> https://maps.google.com/?q=460+TAMPICO,IL+61283&entry=gmail&source=g>> >>> > >>> > *WWW.THEWISP.NET < >>> http://WWW.THEWISP.NET> >>> > <http://WWW.THEWISP.NET> | * >>> > >>> > >>> > >>> >>> > <http://www.thewisp.net/><http://www.facebook.com/thewispnet >>> > <http://www.facebook.com/thewispnet> >>> > >>> <http://www.facebook.com/thewispnet >>> > <http://www.facebook.com/thewispnet>>> >>> > >>> > <http://www.twitter.com/thewispnet >>> > <http://www.twitter.com/thewispnet> >>> > >>> <http://www.twitter.com/thewispnet < >>> http://www.twitter.com/thewispnet>>> >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > On Tue, Oct 30, 2018 at 8:37 AM Josh >>> Luthman via Mikrotik-users >>> > >>> > <mikrotik-users@wispa.org <mailto: >>> mikrotik-users@wispa.org> >>> > >>> <mailto:mikrotik-users@wispa.org <mailto: >>> mikrotik-users@wispa.org>> >>> > >>> <mailto:mikrotik-users@wispa.org >>> > <mailto:mikrotik-users@wispa.org> >>> > >>> <mailto:mikrotik-users@wispa.org <mailto: >>> mikrotik-users@wispa.org>>>> wrote: >>> > >>> > >>> > >>> > CCR goes through two Ubnt wireless >>> links before hitting the RB750. >>> > >>> > >>> > >>> > On the CCR1009 it is ether4 - not a >>> combo port, not switched. >>> > >>> > >>> > >>> > >>> > >>> > Josh Luthman >>> > >>> > Office: 937-552-2340 >>> > >>> > Direct: 937-552-2343 >>> > >>> > 1100 Wayne St >>> > >>> < >>> https://maps.google.com/?q=1100+Wayne+St+%0D%0A+%C2%A0+%C2%A0+%C2%A0Suite+1337+%0D%0A+%C2%A0+%C2%A0+%C2%A0Troy,+OH+45373&entry=gmail&source=g >>> > < >>> https://maps.google.com/?q=1100+Wayne+St+%0D%0A+%C2%A0+%C2%A0+%C2%A0Suite+1337+%0D%0A+%C2%A0+%C2%A0+%C2%A0Troy,+OH+45373&entry=gmail&source=g >>> >> >>> > >>> > Suite 1337 >>> > >>> < >>> https://maps.google.com/?q=1100+Wayne+St+%0D%0A+%C2%A0+%C2%A0+%C2%A0Suite+1337+%0D%0A+%C2%A0+%C2%A0+%C2%A0Troy,+OH+45373&entry=gmail&source=g >>> > < >>> https://maps.google.com/?q=1100+Wayne+St+%0D%0A+%C2%A0+%C2%A0+%C2%A0Suite+1337+%0D%0A+%C2%A0+%C2%A0+%C2%A0Troy,+OH+45373&entry=gmail&source=g >>> >> >>> > >>> > Troy, OH 45373 >>> > >>> < >>> https://maps.google.com/?q=1100+Wayne+St+%0D%0A+%C2%A0+%C2%A0+%C2%A0Suite+1337+%0D%0A+%C2%A0+%C2%A0+%C2%A0Troy,+OH+45373&entry=gmail&source=g >>> > < >>> https://maps.google.com/?q=1100+Wayne+St+%0D%0A+%C2%A0+%C2%A0+%C2%A0Suite+1337+%0D%0A+%C2%A0+%C2%A0+%C2%A0Troy,+OH+45373&entry=gmail&source=g >>> >> >>> > >>> > >>> > >>> > On Tue, Oct 30, 2018 at 11:33 AM, >>> Scott <lamb...@lambertfam.org <mailto:lamb...@lambertfam.org> >>> > >>> <mailto:lamb...@lambertfam.org <mailto: >>> lamb...@lambertfam.org>> >>> > >>> > <mailto:lamb...@lambertfam.org >>> > <mailto:lamb...@lambertfam.org> >>> > >>> <mailto:lamb...@lambertfam.org <mailto: >>> lamb...@lambertfam.org>>>> wrote: >>> > >>> > >>> > >>> > On 2018/10/30 09:24, Josh >>> Luthman wrote: >>> > >>> > >>> > >>> > There are two Ubnt backhauls >>> between them. >>> > >>> > >>> > >>> > >>> > >>> > With recent firmware it >>> shouldn't be a big deal to run >>> > >>> > broadcast. I always run >>> Point-to-point over wireless links with >>> > >>> > exactly two endpoints. A lot of >>> that is leftover from when most >>> > >>> > 802.11 based wireless links had >>> issues with broadcast. >>> > >>> > >>> > >>> > What connects the two >>> backhauls? Crossover cable? Switch, >>> > >>> > smart or dumb, brand? >>> > >>> > >>> > >>> > Which interface are you using on >>> the 1009? Is it a combo port? >>> > >>> > Is it in the switch group? >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > -- >>> > >>> > Scott Lambert >>> KC5MLE Unix >>> > >>> > SysAdmin >>> > >>> > lamb...@lambertfam.org <mailto: >>> lamb...@lambertfam.org> >>> > >>> <mailto:lamb...@lambertfam.org <mailto: >>> lamb...@lambertfam.org>> >>> > >>> <mailto:lamb...@lambertfam.org >>> > <mailto:lamb...@lambertfam.org> >>> > >>> <mailto:lamb...@lambertfam.org <mailto: >>> lamb...@lambertfam.org>>> >>> > >>> > >>> > >>> > >>> > >>> > >>> _______________________________________________ >>> > >>> > Mikrotik-users mailing list >>> > >>> > Mikrotik-users@wispa.org <mailto: >>> Mikrotik-users@wispa.org> >>> > >>> <mailto:Mikrotik-users@wispa.org <mailto: >>> Mikrotik-users@wispa.org>> >>> > >>> <mailto:Mikrotik-users@wispa.org >>> > <mailto:Mikrotik-users@wispa.org> >>> > >>> <mailto:Mikrotik-users@wispa.org <mailto: >>> Mikrotik-users@wispa.org>>> >>> > >>> > >>> > >>> >>> http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users> >>> > >>> < >>> http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users>> >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> _______________________________________________ >>> > >>> > Mikrotik-users mailing list >>> > >>> > Mikrotik-users@wispa.org <mailto: >>> Mikrotik-users@wispa.org> >>> > >>> <mailto:Mikrotik-users@wispa.org >>> > <mailto:Mikrotik-users@wispa.org>> >>> > >>> > >>> > >>> http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users> >>> > >>> < >>> http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users>> >>> > >>> > >>> > >>> >>> _______________________________________________ >>> > >>> Mikrotik-users mailing list >>> > >>> Mikrotik-users@wispa.org <mailto: >>> Mikrotik-users@wispa.org> >>> > >>> <mailto:Mikrotik-users@wispa.org >>> > <mailto:Mikrotik-users@wispa.org>> >>> > >>> http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users> >>> > >>> < >>> http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users>> >>> > >>> >>> > >>> >>> > >>> _______________________________________________ >>> > >>> Mikrotik-users mailing list >>> > >>> Mikrotik-users@wispa.org <mailto: >>> Mikrotik-users@wispa.org> >>> > >>> <mailto:Mikrotik-users@wispa.org >>> > <mailto:Mikrotik-users@wispa.org>> >>> > >>> http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users> >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users>> >>> > >>> >>> > >>> >>> > >>> _______________________________________________ >>> > >>> Mikrotik-users mailing list >>> > >>> Mikrotik-users@wispa.org <mailto:Mikrotik-users@wispa.org> >>> > <mailto:Mikrotik-users@wispa.org <mailto:Mikrotik-users@wispa.org >>> >> >>> > >>> http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users> >>> > >>> < >>> http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users>> >>> > >> >>> > >> _______________________________________________ >>> > >> Mikrotik-users mailing list >>> > >> Mikrotik-users@wispa.org <mailto:Mikrotik-users@wispa.org> >>> > <mailto:Mikrotik-users@wispa.org <mailto:Mikrotik-users@wispa.org >>> >> >>> > >> http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users> >>> > >> <http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users>> >>> > >> >>> > >> >>> > > >>> > > _______________________________________________ >>> > > Mikrotik-users mailing list >>> > > Mikrotik-users@wispa.org <mailto:Mikrotik-users@wispa.org> >>> > <mailto:Mikrotik-users@wispa.org <mailto:Mikrotik-users@wispa.org >>> >> >>> > > http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users> >>> > > <http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users>> >>> > > >>> > > >>> > > >>> > > >>> > > _______________________________________________ >>> > > Mikrotik-users mailing list >>> > > Mikrotik-users@wispa.org <mailto:Mikrotik-users@wispa.org> >>> > > http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users> >>> > > >>> > _______________________________________________ >>> > Mikrotik-users mailing list >>> > Mikrotik-users@wispa.org <mailto:Mikrotik-users@wispa.org> >>> > http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> > <http://lists.wispa.org/mailman/listinfo/mikrotik-users> >>> > >>> > >>> _______________________________________________ >>> Mikrotik-users mailing list >>> Mikrotik-users@wispa.org >>> http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> >> > _______________________________________________ > Mikrotik-users mailing list > Mikrotik-users@wispa.org > http://lists.wispa.org/mailman/listinfo/mikrotik-users > -- -RickG
_______________________________________________ Mikrotik-users mailing list Mikrotik-users@wispa.org http://lists.wispa.org/mailman/listinfo/mikrotik-users
