Linus Färnstrand

We don't have ETAs for our software. The next Android release is anything between a week and a few months away. Initially custom DNS will only work with **local** resolvers....

> A great thing is that Mullvad servers accept WireGuard connections on ports 53, 4000-33433, 33565-51820 and 52000-60000 (which was an information surprisingly hard to find I forwarded this feedback...

We don't have any Snap support to drop. Any Snap package you find is a third party package. We only distribute the Linux app via the RPM and DEB files...

> Arch distro, and while the GUI client is available through AUR, it's not maintained by Mullvad, is it? Correct. The AUR packages are not maintained by us! Regarding `mullvad-vpn-bin`...

> @faern Are there any plans on splitting the application accordingly, instead of putting everything into a single package? In other words, splitting the daemon which needs root access, and...

How/where do you suggest we install the `mullvad-daemon` part of our application on a system with read-only root?

Hmm. We keep our daemon logs in `/var/log/mullvad-vpn`. Maybe something with electron-builder causes unexpected files to be spread out? After install we really should not write to anything except `/etc/mullvad-vpn`,...

Do you mean we connect to our WireGuard relays over IPv4? You can change that under Settings -> Advanced -> WireGuard settings -> IP version. But yes, by default it...

Ok. Is this a problem? Why do you want it to use IPv6?

Ok. I suppose it would be a per-OS thing we would have to do where we would have to announce that the tunnel interface should prefer IPv6. But still I...