[GH-ISSUE #101] Peer-specific obfuscation parameters #54

New issue

Closed

opened 2026-10-13 21:03:07 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-13 21:03:07 +00:00

Owner

Originally created by @Xetera on GitHub (Nov 9, 2025).
Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-go/issues/101

Hi, I'm building a tool on top of amneziawg-go that allows connecting a user to multiple different peers, some of whom should be able to decide to use regular wireguard instead of amnezia. I figured since these settings only have to be shared between 2 peers, they could be set at the peer-level but unless I'm mistaken that's not an option. It has to be declared at the interface level and the same parameters must be shared among every peer in the network.

I'm aware that only using Jc, Jmin and Jmax would be backwards compatible with regular wireguard clients, but I don't think that would be enough to bypass most DPI. Is there any technical reason these parameters can't be configured per-peer?

Originally created by @Xetera on GitHub (Nov 9, 2025). Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-go/issues/101 Hi, I'm building a tool on top of amneziawg-go that allows connecting a user to multiple different peers, some of whom should be able to decide to use regular wireguard instead of amnezia. I figured since these settings only have to be shared between 2 peers, they could be set at the peer-level but unless I'm mistaken that's not an option. It has to be declared at the interface level and the same parameters must be shared among every peer in the network. I'm aware that only using Jc, Jmin and Jmax would be backwards compatible with regular wireguard clients, but I don't think that would be enough to bypass most DPI. Is there any technical reason these parameters can't be configured per-peer?

bsakaguchi closed this issue

2026-10-13 21:03:07 +00:00

bsakaguchi commented

2026-10-13 21:03:08 +00:00

Author

Owner

@ygurov commented on GitHub (Nov 25, 2025):

Hi
We have dropped that functionality for peers during preparations for awg2 due to the code complexity which goes with the feature. The most significant is the incoming traffic handling mechanism which becomes less transparent to implement and understand.
Regarding your problem, I would suggest to create another device on another port which would host a common wireguard solution. You could even use a common wireguard-go instead

@ygurov commented on GitHub (Nov 25, 2025): Hi We have dropped that functionality for peers during preparations for awg2 due to the code complexity which goes with the feature. The most significant is the incoming traffic handling mechanism which becomes less transparent to implement and understand. Regarding your problem, I would suggest to create another device on another port which would host a common wireguard solution. You could even use a common wireguard-go instead

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

amnezia-vpn/amneziawg-go#54

No description provided.

Rows
Columns