-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UBNT Nanobeam AC Gen2 - Unspported Device #768
Comments
Randy, the screenshot shows it as a Nanostation AC Gen1. That may be different enough from the Gen2 to cause these symptoms, |
I'm building a new image for this device as we speak. |
New build submitted here - #770 |
So what it shows INTERNALLY is not what it shows externally.
The box it came in and the device itself are labelled as Nanobeam AC GEN2
Weird. Look at that test date: April 25, 2017
…-Randy



On Mar 29, 2023, at 12:59, Tim Wilkinson ***@***.***> wrote:
New build submitted here - #770 <#770>
Would be good to get this tested as its a bit of a guess in places.
—
Reply to this email directly, view it on GitHub <#768 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIODNVWITSK2R3KSVMYVPD3W6RZ6LANCNFSM6AAAAAAWMDCDAY>.
You are receiving this because you authored the thread.
|
The name we display is what device firmware we load onto the device, not what the device actually is. Bit confusing. |
Tried loading the new (NB 2475) Gen 2 build, That did not work. Loaded the NanoBeam AC Gen 1 firmware and that was successful. Able to configure and run normally. Very annoying that the labels on the device show Gen2 very clearly but this is actually a Gen 1 device. |
Hmm. I should still make that gen 2 build work. How did it fail? |
It failed in the same way as before. Bad Gateway trying to reach /cgi-bin/setup
I did have to load the file to /tmp and do a sysupgrade after logging on as root since their was an existing (partially failed) AREDN install from the previous attempt.
… On Mar 30, 2023, at 13:00, Tim Wilkinson ***@***.***> wrote:
Hmm. I should still make that gen 2 build work. How did it fail?
—
Reply to this email directly, view it on GitHub <#768 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIODNVRYDF2QLM76GW4VM5TW6XC5LANCNFSM6AAAAAAWMDCDAY>.
You are receiving this because you modified the open/close state.
|
After closing issue #757 I browsed to the device to begin configuring it.
Device showed Unsupported device message this is detailed below. Attempts to get to the Setup page resulted in error message "Bad gateway"
The text was updated successfully, but these errors were encountered: