What's new

[384.16_Alpha Builds] Testing all variants

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Ahh, so in the changelog:
- UPDATED: Merged GPL 384_8137 and binary blobs 384_7968
for RT-AX88U.

The GPL is the code you compile and the binary blobs are just that.. binaries you get?
So the fixes they mention in the changlog are in the GPL and not the binaries.

Some portions of the code are closed source (like the wireless drivers). These are what I call "binary blobs", as I receive them in pre-compiled form as part of a GPL release. These are model specific, which means if a newer GPL is released for a different (like in this case, 8137 was released for the RT-AX58U), then I can only reuse the open source parts of that release, and must keep the binary components from the last release for the model which I support (in this case for the RT-AX88U, it means 7968).
 
Some portions of the code are closed source (like the wireless drivers). These are what I call "binary blobs", as I receive them in pre-compiled form as part of a GPL release. These are model specific, which means if a newer GPL is released for a different (like in this case, 8137 was released for the RT-AX58U), then I can only reuse the open source parts of that release, and must keep the binary components from the last release for the model which I support (in this case for the RT-AX88U, it means 7968).

Makes sense. Curious how long from Asus releasing a firmware to you getting the GPL package? Ie. how long to get the wireless drivers for 7977 released from 20.
 
Makes sense. Curious how long from Asus releasing a firmware to you getting the GPL package? Ie. how long to get the wireless drivers for 7977 released from 20.

It varies greatly. Sometimes it's 24 hours, sometimes it's 2 months. In the case of 7968, I only got the GPL on February 19th. I still don't have the 7977 GPL. So could be this week, or could be in a few months.
 
No issues to report with 384.16_alpha1-ga40d2d5f30 after 4 days uptime on my AC86U (main) and AC68U (mesh node) :)
 
My RT-AX88U running 7977 has wireless driver version wl_version=17.10.99.1302 (r779368) .
On .16 Alpha I get version 17.10.99.1302 (r779368).

So that didn't change. For some reason the file is called .W on the share, but I renamed to .trx and it worked.
 
My RT-AX88U running 7977 has wireless driver version wl_version=17.10.99.1302 (r779368) .
On .16 Alpha I get version 17.10.99.1302 (r779368).

So that didn't change. For some reason the file is called .W on the share, but I renamed to .trx and it worked.
Your AX88U uses the .w firmware.
 
My RT-AX88U running 7977 has wireless driver version wl_version=17.10.99.1302 (r779368) .
On .16 Alpha I get version 17.10.99.1302 (r779368).

So that didn't change. For some reason the file is called .W on the share, but I renamed to .trx and it worked.
AX88U using 384.15 and the driver version is also 17.10.99.1302 (r779368)
 
Alpha 384.16 on RT-AX88U + 2x RT-AC86U in back-haul AiMesh mode. Smart Connect - Disabled. SSID on 2.4GHz & 5.0GHz different. After dirty upgrade from 384.15 the 5GHz light on the router didn't come on. After 10mins, power off/on AX88U Router, no change. After 10mins, reloaded the AX88U Alpha firmware, no change. The Wireless log showed...
upload_2020-2-26_15-55-57.png

The setup for 5GHz band had the control channel at 0 and Auto. You could not alter the Auto.
upload_2020-2-26_15-56-55.png

After changing the SSID of the 5.0GHz to something else, the white 5.0GHz light on the RT-AX88U then enabled (yippee). Then after 10mins...changed the SSID back again, and all ok and has been ever since (3 days).
 
Can someone please ELI5 what this means? "Merged GPL 384_8137 and binary blobs 384_7968 for RT-AX88U"
 
I tried the latest one for the AX88U, but it seems it couldn't get a IPv4 lease through PPPoE anymore. Remarkably IPv6 worked fine, my provider has native IPv6
 
What new changes?
Code:
* 2019-12-20: Version 1.6.0-beta.1
  * Migration of build system to cmake. Build now works on Ubuntu,
    Windows 10 and macOS.
    Some notes on minor differences in the new cmake build:
      * OpenSSL 1.0.2 or higher is now required
      * libunbound 1.5.9 is now required
      * Only libidn2 2.0.0 and later is supported (not libidn)
      * Windows uses ENABLE_STUB_ONLY=ON as the default
      * Unit and regression tests work on Linux/macOS
        (but not Windows yet)
Code:
* 2019-12-20: Version 0.3.0-beta.1
  * Migration of build system to cmake.
 
On an odd note with my AX-88U, updated it and went to change some settings (disable SSH) and for some reason it kept erroring up to the "Router Login Name" and would not let me use my numerical 384.15 login name.
I previously was using a string of numbers as the login name, along with a randomly generated password.
Now it requires alphanumeric and won't let me do numeric only.

Has anyone else experienced or noticed this?
 
Yea they just released it apparently it isn't beta anymore.
From the GetDNS page:

This release has a Stubby version 0.3.0-rc.1 included, also modified for the CMake build tools and updated with a few fixes.

Please review these release candidates carefully, if all is well, the actual release will follow Friday the 28th of February.

By my clock it is not 28FEB...yet!
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top