Is this the Lite Beam listed on the Aredn Matrix as usable? https://www.amazon.com/LiteBeam-LBE-5AC-Gen2-Ethernet-Protector-High-Spe...
Thank you.
Thank you.
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
The LBE-M5-23 is supported by AREDN and OpenWRT v19.07.8.
The LBE-5AC-Gen2 is supported by OpenWRT v21.02.1, but not yet BY AREDN.
https://openwrt.org/toh/start?dataflt%5BBrand*%7E%5D=ubiquiti
I hope this helps,
Chuck
73,
Specifically ... does AREDN MESH firmware exist / run on the Ubiquiti LiteBeam LBE-5AC-Gen2 ?
No, not now.
Everyone: I do not recommend to buy unsupported equipment and hope for it to be added later.
Chuck
Andre, K6AH
We playmakers buy every new product. However, the search for cheap products continues to establish more stations throughout the country. We are waiting for your good news about this model.
Orv W6BI
I have two. They work fine in a test setup.
73, Chuck
I successfully flashed a LiteBeam 5AC LR with the latest release (3.25.5.1) and noticed it only supports Wireguard tunnels. Hoping to downgrade to an earlier firmware that perhaps still supported the legacy tunnel, I selected the oldest listed choice in the upgrade drop-down menu, 3.24.4 I think, thinking since it was listed there it must be safe. The downgrade proceeded but the screen never refreshed. I manually refreshed after 10 minutes and the node would not come up. In retrospect, should I have tried to access it with a static 192.168.1.1 at that point? I had it dtd'd to another node so had turned off its dhcp server which further complicated the issue since now I could not try to access it with localnode.local.mesh. The node was visible from both the dtd node and an rf node but unreachable from either one. I tried a 5-second and a 30-second reset as well as a reset by applying power after pushing the reset and holding for 30 seconds. As expected, it is now not visible from other nodes. It won't ping when forced a static 192.168.1.1 or 20 address. So of course I can't ssh with either of those addresses to maybe side load an upgrade. And of course its dhcp server was turned off prior to the downgrade so no dynamic address either. I'm fresh out of ideas! If this can be rectified, is it possible to still load the vtun package and use the legacy tunnel on the newer firmware? Vtun is not on the package list for this device. if not, no big deal, I can continue the dtd with my legacy node that still uses the legacy tunnel until at such time it is no longer necessary.
"Dont allow new legacy tunnels #2005 (aanon4) 2025-03-19"
Try 3.25.2.0 with a fresh factory.bin .
73, Chuck
Is there a reason you don't want to use a WG tunnel? Lots of plusses and not much of negatives (unless you are trying to connect to some other node that is years out of date).
One way to remain on recent firmware but retain a legacy tunnel would be to pull out an old device that supports it and use it just to support the legacy tunnel. This is a band aid and won't work forever but would get that node back online ... today. The real fix is to get the other end of the tunnel onto Wireguard.
You can buy a GL-iNET router for less than $40 and run it from USB power ... cheap and easy way to have an older firmware available. However this is a temp fix only.
Ed