#Mullvad DAITA not working
1 messages · Page 1 of 1 (latest)
Nothing to do with us. Please contact Mullvad support for any issues regarding their product.
As you can see from their website, they seem to indeed have issues with DAITA currently.
That's a coincidence that they actually have issues right now, because it hasn't been working for me for a whole while now. I just had not filed a ticket until now. On other platforms like iOS and MacOS it works however, just not on Secureblue.
I'm using Mullvad DAITA right now on secureblue and it's working fine for me
So that means something in our settings is different, that makes it work for you but not for me. That's what I'm trying to figure out
It is still not working for me. Does anyone have an idea how to fix it?
not sure. I haven't done anything special with my mullvad configuration, I layered the mullvad CLI (no GUI) and haven't messed with the tunnel configuration settings much. according to mullvad status the features I have enabled are:
DAITA, Dns Content Blocker, LAN Sharing, Lockdown Mode, Quantum Resistance
the one unusual custom thing I've done is applying a lot stricter systemd sandboxing to mullvad-daemon.service, but that's only restricting access, not granting it, so I don't see how that could account for the difference
Is it normal that when I turn on DAITA, the connection will not show up in the GNOME network interface? Whereas when it's turned off, I can see it there?
So my connection does work now with DAITA and according to the Mullvad website I am connected. But I have no idea why it doesn't show that I'm connected in the GNOME settings. But that was already the case when I used regular Fedora Workstation with GNOME in the past, so maybe it's just a GNOME thing
Anyway, thank you for your help. Although I didn't change anything, it just suddenly works now again. Idk what the issue was 😅