Unable to Set Multihop Entry Location

[Exitium-DEV]

Is it a bug?

• I know this is an issue with the app, and contacting Mullvad support is not relevant.

I have checked if others have reported this already

• I have checked the issue tracker to see if others have reported similar issues.

Current Behavior

Following the official CLI guide I attempted to set an entry location of gb and an exit location of nl.
This did not succeed.

https://mullvad.net/en/help/cli-command-wg

$ mullvad relay set location nl
Relay constraints updated

$ mullvad relay set tunnel wireguard entry location gb
Relay constraints updated

$ mullvad connect
$ mullvad status -v
Connected
    Relay:                nl-ams-wg-003 (185.65.134.83:51820/UDP) via nl-ams-wg-201 (169.150.196.2:49794/UDP)
    Features:             DAITA, Dns Content Blocker, LAN Sharing, Multihop, Quantum Resistance
    Bridge type:          None
    Tunnel type:          WireGuard
    Tunnel interface:     wg0-mullvad
    Visible location:     Netherlands, Amsterdam

Expected Behavior

$ mullvad status -v
Connected
    Relay:                nl-ams-wg-003 (185.65.134.83:51820/UDP) via **gb-lon-wg-008**
    Features:             DAITA, Dns Content Blocker, LAN Sharing, Multihop, Quantum Resistance
    Bridge type:          None
    Tunnel type:          WireGuard
    Tunnel interface:     wg0-mullvad
    Visible location:     Netherlands, Amsterdam

Steps to Reproduce

Commands above.

Failure Logs

Operating system version

Debian 13

Mullvad VPN app version

mullvad-cli-status 2025.10

Additional Information

No response

[Exitium-DEV]

Maybe related to #7103 (comment) by @Serock3
I wonder if the CLI is overriding the entry node due to DAITA?

[Exitium-DEV]

Indeed the above was the issue.

$ mullvad tunnel set wireguard --daita-direct-only on

The above solved the problem. I'm going to leave this open as a documentation feature request, at least if only for the guide referenced above as nobody would've figured that out without scouting GitHub like myself.

[Serock3]

You're right that the entry relay is being overwritten by DAITA. That's an oversight in the guide for sure, and also poorly communicated in the CLI. We'll make sure to update the guide, and I'll look into if the output of mullvad status in this scenario can be clarified a bit too. Thanks for the feedback!

[Serock3]

The mullvad status command was updated in #9686, and a reworked version of the guide is coming up shortly. Thanks for the report ✨