So no AmneziaWG support for this model? Not even via plugins?
I upgraded my Slate 7 to the current beta 2026-04-11.
I can’t reach my Slate Plus which acts as a wireguard client on a different network.
It worked without any issues before with fw 4.8.3
Checked every toggle and Route Rules are there as intented on my Slate 7.
Slate Plus is online and reachable from a mobile device.
Also the green dot on the wireguard server connected devices page on my Slate 7 is visible.
Was excited until i seen flint 2 wasn’t available yet, looking forward to that release especially with all the bugs the previous versions have been having with hardware acceleration/dns/ipv6 hopefully soon… flint 2 runs great on openwrt 25.12.2 btw.
Can I kindly ask to move the usual “my several years old device isn’t getting any updates, shame on you” derail on a dedicated thread instead of derailing this one? I’m curious to see how the 4.9 beta fares but I don’t want to pop in here after seeing new posts just to read noise. If you want up do date openwrt code on devices not on 4.8 already, you only need to go https://firmware-selector.openwrt.org type your model and download the sysupgrade file, and it’s easily reversible.
Q2: When will these features be available, and on which devices?
A2: After the testing phase, we plan to gradually roll out these features to more device models, depending on their hardware capabilities and performance.
I cant find the post (not sure if it was here or reddit). but they were doing other hardware in a phase approach over 2026 when it comes to 4.9. In the post they mentioned GL-AXT1800 and some other models however we will see what devices actually get it. (im not holding my breath on anything)
That is why moving forward ill only be purchasing devices that have vanilla openwrt support. So when they eventually move on I can still update my device
Will the Brume 2 get a v4.9 update, or do I need to buy the Brume 3 to get v4.9 in the future? The Brume 2 is enough for my use case, and si I’m hoping it will also receive v4.9.
Absolutely agree, and this reflects our priorities exactly. Stability, security, and consistency across all supported models are the foundation we're building on — features come after we get those right.
For 2026, we're committed to ensuring that every firmware release meets a higher bar for quality assurance and documentation before it ships. That means more rigorous testing across the full range of supported hardware, clearer changelogs, and better communication when things change.
Thank you for articulating this so well — feedback like this helps keep us focused on what matters most.
I just found that Adguard Home isn't working with Mullvad WG Client if you enable it while Mullvad tunnel is running.
If Mullvad WG client is running and I try to enable Adguard Home, it simply redirects to Mullvad DNS even if using encryted DNS.
To make it work, Mullvad Tunnel must be disabled and I have to FIRST start Adguard Home and THEN Mullvad Tunnel and then it works.
