Why does the same WireGuard client configuration file work perfectly on the MT3000 but fail to work on the MT3600BE?

[Thomas99]

When the same configuration file is uploaded to the MT3000, the WireGuard client works perfectly;
however, when uploaded to the MT3600BE, the WireGuard client fails to work.
Why?
The log on the MT3600BE shows:

Thu Apr 23 18:48:44 2026 daemon.notice procd: /etc/rc.d/S95vpn-client: Found matching instance wgclient1 for rule peer: 2001
Thu Apr 23 18:48:44 2026 daemon.notice procd: /etc/rc.d/S95vpn-client: Stopping instance wgclient1 (all rules disabled)

My two devices have same settings; IPv6 is not enabled, and I’m using Global Mode.

How should I resolve it?

Thank you all for your help.

[RBzee]

Do you have obfuscation parameters set? The MT3000 supports Amnezia 2.0, while the MT3600BE doesn’t yet.

[Thomas99]

Thank you for your reply.

I haven’t configured any “obfuscation parameters.”

I’m only using the “WireGuard Client” because the WireGuard Server service is provided by VPN service providers. They do not provide obfuscation parameters.

[lucas2]

What firmware version is your MT3600BE?

Could you provide me with a profile so I can verify it on my MT3600BE?

Or could you export the complete VPN connection failure logs and send them to us for review?

If it's inconvenient to do this here, you can send your log or profile to support@gl-inet.com along with a link to this post.

Thank you.

[RBzee]

Does your configuration contain any lines like these?

These are AmneziaWG 2.0 obfuscation parameters. The MT3600BE currently supports AWG 1 or 1.5