Lost RF on one node after upgrading to nightly build 20231211-d697fc0

[CoolAEW]

Describe the bug

After upgrading to 20231211-d697fc0 one of my 2 nodes lost contact on RF.
Both nodes are Ubiquiti NanoBeam AC Gen2 and are fairly similar in setup, both linking to 1 node each on RF and have DtD connection between them. Only one node have lost RF, the other works.

• Does this issue still occur on the latest version? (Required)
  Does not occur on 3.23.12, only nightly

Expected behavior

Normal upgrade with functioning links

Screenshots

Additional context

None

[aanon4]

What does the neighbor information look like?

[CoolAEW]

LA3T-20-1 (Problem node)

LA3T-20-2 (Working node)

I should add that reverting to 3.23.12 fixes the issue, but I have reinstalled nightly for testing

[aanon4]

So, when working, these nodes should show the identical stuff?

[CoolAEW]

No, they link with one node each plus the DtD, I expect to see a link to "LA3T-26" from "LA3T-20-1"

[aanon4]

When you restore 3.23.12.0 (I assume you will) could you post the same data? Also, if you could post the support data for the problem node both with nightly and with 12 that would be helpful too.

[CoolAEW]

Downgraded to 12, this is how it looks now.

supportdata-LA3T-20-1-3.23.12.0-202312112003.gz
supportdata-LA3T-20-1-NIGHTLY-202312111946.gz

[aanon4]

Thanks.
Two things. First, it would be really interesting to know what kind of hardware is on the other end of the link which works, and the one which doesnt.
Second. Could you try the next nightly build? This uses the same radio firmware as the release; the current nightly does not. It would be good to see if that's the issue here.

[CoolAEW]

Both remote nodes are Ubiquiti NanoBridge M5
I'll try the next nightly when it's released.

Also, here's the support data from the node which is currently working with the current nightly build.
supportdata-LA3T-20-2-NIGHTLY-202312121620.gz

[aanon4]

Thanks.
A new nightly should be available to test.

[CoolAEW]

Loaded the newest nightly and that seems to have resolved the issue.

[aanon4]

Could I send you a custom build to also try?

[CoolAEW]

Yes, send it over and I'll download it later today

[aanon4]

aredn-kn6plv-wireless-mon-ac-e7181b73-ath79-generic-ubnt_nanobeam-ac-gen2-squashfs-sysupgrade.bin.zip

Give this a try when you have a moment. Please give it 5 minutes (ie plenty of time) to make a connection after it reboots on the node previously not connecting over wifi.

There's a bug in the firmware for Mikrotik which requires some workarounds in AREDN to make it connect when it initially fails. As this Ubiquiti firmware also comes from the same provider, it's possible it has the same bug. I've enabled the workaround here to test this idea. Thanks for helping out - much appreciated.

[CoolAEW]

Ok, tried the build now and gave it 20mins, but it still haven't connected to the remote node. It shows up in the mesh status list, but only with IP. On the neighbours list it shows as Idle.


supportdata-LA3T-20-1-202312132349.gz

[aanon4]

Thanks. I guess this firmware isn't viable then.

[aanon4]

If you have a moment to try today's nightly on your nodes, that'd be fantastic.

[CoolAEW]

20231214-b2fb79d?
I just installed it, it works.

[aanon4]

Yes, and thanks. I'll close this now.