Skip to content

Implement new params for AmneziaWG 1.5 #815

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Implement new params for AmneziaWG 1.5 #815

wants to merge 3 commits into from

Conversation

hinakumo
Copy link
Contributor

New parameters: I1, I2, J1, J2, J3, Itime

amnezia-vpn/amneziawg-go@c207898

@donaldzou
Copy link
Owner

I'm holding off changing AWG until issues are fixed for amneziawg-tools

@donaldzou
Copy link
Owner

But still, thank you for providing this PR :)

@DaanSelen
Copy link
Collaborator

Love to see the community helping out. Thank you.

@hinakumo
Copy link
Contributor Author

I have added another Dockerfile that changes amnezia-wg to commit c20789848019fb494dbe9d280eb246f29b95ab85 and compiles (instead of downloading build) amneziawg-tools with commit ae857090cdef53919ed197c477869544780fc6eb, because they have reverted v1.5 changes.

But I also think that it's the right choice to download specific commits instead of using master everytime, because there will be many breaking changes, especially in the 2.0 version:
изображение

I agree that it shouldn't be merged until they fix these problems and return back v1.5. But, now we are ready for the upcoming changes, and we can test how it works ✨

@donaldzou
Copy link
Owner

Or... maybe I should just fork my own AWG and AWG tools lol, to prevent something happen like that agian

@hinakumo
Copy link
Contributor Author

Or... maybe I should just fork my own AWG and AWG tools lol, to prevent something happen like that agian

The main problem with Amnezia is that they rarely test anything. For example, until very recently, their repositories contained broken DKMS packages that caused compilation errors during installation and broke commands like apt update. This was fixed only after a huge number of complaints and desperate attempts to reach the developers via Telegram chat.

I like that thanks to Amnezia, users from countries with high censorship (like me) have access to the free Internet, but unfortunately, at the moment it is not an enterprise-ready stable solution like WireGuard.

A week ago, they pushed an update adding v1.5 to the master branch without testing it properly. This led to the fact that the amneziawg-tools release included code with a broken parser, which made it impossible to start interfaces.

Now they fixed it, but removed support for v1.5 (nobody knows why), not giving us the opportunity to fully adapt to the protocol changes. So I had to specify in the Dockerfile specific commits where the parsing bugs were fixed, but the new v1.5 parameters still worked.

So, I hope that someone like you will fork amneziawg, amneziawg-go, amneziawg-tools and make a stable solution, where each update will be properly checked and unstable code will not get into release branches 🙏

@donaldzou
Copy link
Owner

donaldzou commented Jul 12, 2025 via email

@hinakumo
Copy link
Contributor Author

I guess they’re trying to focus to earn revenue through their app (which have comprehensive doc on it)

They are now selling Premium subscription with v1.5 mostly for users in Russia, because DPI filtering has become much worse. On specific events (like SPIEF), mobile Internet access to global services in that city was completely cut off, especially near the ExpoForum area.

Only government and local services were working. But, some VPN services that were using VLESS and other protocols with SNI spoofing were working, so now they are planning on implementing that in AWG 2.0.

I understand that they want to make money by selling paid subscriptions, but I don't understand why they are breaking things by pushing untested broken updates, removing previously announced functionality and then telling users to buy paid service, because it's working. That's just unprofessional 😕

I’ll fork all 3 of them and roll them back to the 2024 commits until people are happy with v1.5, so we can just clone the main branch on my fork instead of cloning a specific commit.

Looks like a great idea, but 2024 was 7 months ago and they have changed a lot of things for DPI circumvention from that time. So I think it's better to use code from 2 or 3 months ago. But it's your choice, I like your project and I will be happy to help 👐

@donaldzou
Copy link
Owner

donaldzou commented Jul 12, 2025 via email

@donaldzou
Copy link
Owner

Hi @hinakumo , I forked all 3 repos under the WGDashboard organization:

and created tag stable, maybe we can use that instead in the dockerfile

@hinakumo hinakumo mentioned this pull request Jul 12, 2025
Closed
@hinakumo
Copy link
Contributor Author

and created tag stable, maybe we can use that instead in the dockerfile

Hi, that's great! I have created another PR which changes links to your repos in Dockerfile: #818

@donaldzou
Copy link
Owner

donaldzou commented Jul 12, 2025 via email

@Arunachalamkalimuthu
Copy link

@donaldzou Can we merge this PR?

@donaldzou
Copy link
Owner

@donaldzou Can we merge this PR?

Not until i fully tested the new AWG

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@hinakumo @donaldzou @DaanSelen @Arunachalamkalimuthu