Skip to content

fix: pass S3/S4 params for all AWG containers, not only Awg2#2648

Open
artmchk-pixel wants to merge 1 commit into
amnezia-vpn:devfrom
artmchk-pixel:fix/awg-s3-s4-third-party-config
Open

fix: pass S3/S4 params for all AWG containers, not only Awg2#2648
artmchk-pixel wants to merge 1 commit into
amnezia-vpn:devfrom
artmchk-pixel:fix/awg-s3-s4-third-party-config

Conversation

@artmchk-pixel
Copy link
Copy Markdown

Problem

cookieReplyPacketJunkSize and transportPacketJunkSize (S3/S4) were only
set when container == DockerContainer::Awg2. This caused AWG 2.0 to not
work for third-party imported configs (vpn:// links) on Linux because
those use DockerContainer::Awg.

Root cause

In awgConfigurator.cpp, S3/S4 were wrapped in:
if (container == DockerContainer::Awg2) { ... }

Fix

Remove the condition so S3/S4 are always passed regardless of container type.

Fixes #2219

cookieReplyPacketJunkSize and transportPacketJunkSize (S3/S4) were only
set when container == DockerContainer::Awg2. This caused AWG 2.0 to not
work for third-party imported configs (vpn:// links) on Linux and other
platforms since those use DockerContainer::Awg.

Fixes: transport data blocked with AWG 2.0 servers (issue amnezia-vpn#2219)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AmneziaVPN app does not pass S3/S4 to amneziawg-go — transport data blocked with AWG 2.0 servers

1 participant