It will not receive an upgrade at the beginning of the Beta phase. It will receive the release version early, before it is released as stable.
You can upload it with your browser or with our App. The risk has nothing to do with the client device, it only depends on how stable the firmware is. If there is a problem with the upload, it will prevent the upgrade.
Its complexity does not originate from the coding part. It comes from the environment.
If we launch a feature that looks simple, then users with no technical background will try to use it. They don't have the same technical knowledge as you do. For them, the feature will be random: it will work for some clients, it will not work for some clients (devices that don't support it). They will question it and will think something is wrong. We'll have to explain it over and over again.
So we're thinking of making a kind of lab page for features that have a threshold of use to provide, something like chrome://flags.
Just add an optional toggle button "show wake on lan options", default off, if you enable it, show wake button to each client line in the web gui. Problem solved. Everyone is happy.
Not sure the majority have a need for WOL.
Also, you can't just clutter the Admin UI with enable/disable functionalities..
Pro users can switch to Luci or SSH and be king of their neeeds..
ssh <YOUR_ROUTER>
etherwake <MAC_ADDRESS>
And, there are dedicated topics for feature requests.
@yuxin.zou can you guys add automatic extroot to firmware? To make person just insert SD, click button, and thatâs all.
Thanks for your reply. I appreciate all of the work accomplished by you and your team, the update process was very efficient.
I have not tried the app, I've only used the web browser interface. I will read about the app to learn if there are any new advantages or features.
I updated to 4.6.0 beta3. Will the next versions, such as beta4 update automatically or will I have to update manually if there is another version of the beta before the final release?
The probability of errors in the exroot process is very high, and even if done manually we do not recommend it for those without a technical background. So it is unlikely to be automated.
Beta versions do not automatically push updates to users ...... because we also don't know which of these releases may have issues that make them unusable or even lose settings.
Disclosure: I'm an amateur. But, hey, weren't we all at one time. okay, so I downloaded and installed the Snapshot Firmware for my Brume 2. (Living life on the cutting edge i know! ) I have a sub to AzireVPN. Using the GL-Inet gui to facilitate downloading the wireguard configs i noticed none of them were populated with the "[Interface]" section - just "[Peer]". So they don't work. As a workaround i manually created one that i could use so i'm okay but figured you guys might want to know. Thoughts?
So,.. I'm on new beta verson dated 2024-06-11 and here are my findings (Flint1):
DHCP reserved IP seems to be working for some devices,..
I just installed 4.6.0-op24 2024-06-07 on my MT3000.
The toggle switch to enable/disable the OpenVPN Client doesnât work.
Is this a known issue?
Yes, I have the same issue
Firmware downloads page is showing that version 4.6.0 is the latest stable version for Brume 2 with a beta build of 4.6.1? Is this correct?
Seems odd that 4.6.0 is stable on brume 2 when issues are still arising and other models are still currently on 4.5.16 (as of today)
4.6.1 Brume 2, Adguard don´t blocks Ads. Shown after update to 4.6.1 Beta only Local Host no Client and not blocking Content. Back to 4.6.0 14.6.2024, all is fine.
Yesterday we released the 4.6.0 stable version of brume2. It doesn't have Wi-Fi, so there aren't as many issues ...... I forgot to update it.
Looking at other people's replies,.. I'm guessing
As Firmware gets newer and newer (4.6.0b1, b2, b3, 4.6.1),.. features will die one by one? 
I installed the 4.6.0 snapshot (29240619), and the toggle button works. Maybe itâs an issue with op24? Can anyone confirm?
I am going to need captive portal support in two days (cruise). There are a lot of suggestions than 4.6.0-op24 fixed it, but is 4.6.0 (beta and snapshot) just as good for it?
I know the release notes state as much, but want to confirm with real-world anecdotes before I go. Iâd rather lose toggle button functionality than captive portal functionality.
@yuxin.zou i donât see in release notes fix for tunnel vision:
- Other enhancements
Critical Security Updates
This firmware release fixed a vulnerability tracked as CVE-2023-46456 with a CVSS Score of 9.8. It was possible to inject arbitrary shell commands through the OpenVPN client file upload functionality. CVE-2023-46454 with a CVSS Score of 9.8 was also fixed. It was possible to inject arbitrary shell commands through a crafted package name.
Additionally, this release patched a vulnerability tracked as CVE-2023-46455 with a CVSS Score of 7.5, which could create the possibility of writing arbitrary files through a path traversal attack in the OpenVPN client file upload functionality.
We also fixed CVE-2023-50919 which allowed an NGINX authentication bypass via Lua string pattern matching, and fixed CVE-2023-50920 which potentially allowed the sharing of session identifiers between different sessions and bypassing authentication or accessing control measures.
Will this be fixed?
Hi, I have a Brume 2 and I upgraded to 4.6.
Let's say it didn't go very well, I had to reset to factory settings and reconfigure everything.
Now AdGuard Home no longer shows me the various clients in the search log but only the localhost 127.0.0.1. Is this normal or is it a bug?
