Hello All. Just an FYI I recently encountered in case it is useful to others.
I have a Mikrotik hAP Lite AC router, and connected to the PoE Out port of that router is a Ubiquiti 5AC Gen2 dish as a DtD. Both were running v4.26.7 of the AREDN firmware.
I had recently upgraded just the Mikrotik to v4.26.10. I found that after a few hours, the Ubiquity dish was pingable but its HTTP interface was not responding, and it was no longer connected to its wireless peer (Ubiquiti Rocket 5AC Lite) on the mesh. As a workaround, I would disable the Mikrotik's PoE Out port, count to five-Mississippi, then toggle PoE Out back on. (when in doubt, reboot, right?) All fine for a couple of hours, and then same problem.
When I upgraded the Ubiquiti to match, onto firmware v4.26.10, the problem went away, with no other config changes having been made to either the MIkrotik or the Ubiquiti.
Usually, matching firmware on the DtD is not strictly required, but in this case, there was something in the relevant release that it didn't like.
73,
N7TTT
I have a Mikrotik hAP Lite AC router, and connected to the PoE Out port of that router is a Ubiquiti 5AC Gen2 dish as a DtD. Both were running v4.26.7 of the AREDN firmware.
I had recently upgraded just the Mikrotik to v4.26.10. I found that after a few hours, the Ubiquity dish was pingable but its HTTP interface was not responding, and it was no longer connected to its wireless peer (Ubiquiti Rocket 5AC Lite) on the mesh. As a workaround, I would disable the Mikrotik's PoE Out port, count to five-Mississippi, then toggle PoE Out back on. (when in doubt, reboot, right?) All fine for a couple of hours, and then same problem.
When I upgraded the Ubiquiti to match, onto firmware v4.26.10, the problem went away, with no other config changes having been made to either the MIkrotik or the Ubiquiti.
Usually, matching firmware on the DtD is not strictly required, but in this case, there was something in the relevant release that it didn't like.
73,
N7TTT
