-
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 AirRouter doesn't allow Wi-Fi AP or WAN Nightly tiny 2274 #694
Comments
Tiny builds no longer include support for AP access by default due to the lack of space. The packages can be installed separately if you're in a small enough mesh environment where this wont cause problems. I'll make a note in the README. |
OK - Kinda figured that. Can you point me to which module(s) I need to load in order to restore this function? At least the Wi-Fi AP mode as it is driving our Weather station at one of my repeater sites. |
Look for "wpad-mini" ... not the most obvious name. |
The wpad-mini install did the trick. It also retained my previous AP setting and my Weather Station has reconnected and is reporting properly. On another note, I was able to "revert" another AirRouter tunning N-2074 back to N-2002, which restored the AP capability running the older Nightly firmware. Thanks for the response. Should I wait to close this until you update the README file? This should be a "warning" to folks upgrading to the new OpenWRT tiny nightlies when loss of funtion is involved. |
Let's wait until this PR is merged: |
Please be as specific as possible on critical module functions lost and maybe indicate which module names can restore those functions like the obscure "wpad-mini". I'm aware of Tunnel and now the Wi-Fi AP and WAN functions. |
I'll talk to Steve about adding something to the docs about this - dont want to start listing all the potential packages for various scenarios here. |
That information goes into the Release Notes. The online docs do not contain any information about specific firmware builds or packages -- all of that information is always maintained in the Release Notes. |
We document the port usage per device in the github README. Wherever we
put device specific information, we should try to keep it all together.
Note, device specific details are relevant across many releases. It
doesn't seem to be the best place to put in the notes of a specific
release. Is github the best place?
…On Fri, Feb 3, 2023 at 9:46 AM Steve ***@***.***> wrote:
That information goes into the *Release Notes*. The online docs do not
contain any information about specific firmware builds or packages -- all
of that information is always maintained in the *Release Notes*.
—
Reply to this email directly, view it on GitHub
<#694 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGDKU6KNWEGUPKABCWEKYXLWVVOC7ANCNFSM6AAAAAAUQSRJNQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Ready to close this one? |
Yes. I've moved copies of the release notes we post online into the git so people can easily refer to them here. We'll add appropriate notes when we do the final release. |
Running Nightly 2274 doesn't have the RF Wi-Fi AP nor WAN selections available on units previuosly configured for such operation.
The text was updated successfully, but these errors were encountered: