I haven’t “needed” it yet. I heard it doesn’t work in China “for long” but IDK about awg 2.0
Thank you for the information.
We will have our R&D team review it and consider upgrading kmod-amneziawg version for a future firmware update.
FYI to all.. GL reverted out the AWG2.0 features of the SlateAX 4.8.3-beta firmware when pushing to 4.8.3 stable. (Transparency would be nice btw).
4.8.4-beta should now include AWG2 (going to review tomorrow to see if it has the same broken implementation as 4.8.3-beta did).
I am using 4.8.4 on my slate GLAXT1800 and running the new amezia protocol back to my Flint 3 with 4.9 beta 4 at home without issue so far.
@ChrisC then the client profiles and params must have been generated on the other device. The ones that the SlateAX 4.8.4 autogenerate remain broken. For example, you cannot put spaces in between the H param ranges:
—–
For all.. Slate AX 4.8.4, there’s still several AWG2 issues:
-
kmod is still built on v1.0.20260210, which has several bad (hard freeze) bugs that have been fixed in upstream this past month
-
no support for “I” parameters
-
incorrect formatting for H paramters.
This is still very much alpha/beta support.
Correct I generated the profiles on the flint3.
I installed amnezia wg on my iphone and imported profile. I did the same with my slate ax and imported the profile. Both have been working for past 3 days without issues.
I can also see in Adguard it is filtering that subnet as well.
Additionally I am running Nordvpn on the flint3 which runs Adguard
Could any of these issues cause leakage? That’s more only concern at the moment.
No. The issues I was pointing out would simply be either poor obsfucation or router instability/freezes. The underlying security of the core wireguard tunnel is not impacted.
I guess it’s possible that a router crash/freeze could introduce a tiny momentary leak (hard to say when the OS is crashing), but not something I’d be overly concerned with. I would hope GL rebuilds the kmod against the latest upstream soon, which will fix the instability issues and some of the broken S3/4 param support.

