Incus containers are not assigned IP addresses

simos · July 30, 2024, 2:23pm

MullvadVPN describes here what they are doing with regards to the firewall of your system. In a nutshell, it takes over your firewall and imposes its own firewall rules.

github.com

mullvad/mullvadvpn-app/blob/main/docs/security.md

# Mullvad VPN app security

This document describes the security properties of the Mullvad VPN app. It describes it for all
platforms and their differences. Individual platforms might have slightly different properties and
allow or block network traffic a bit differently, but all such deviations are described here.

This document does not describe in detail *how* we reach and uphold these properties, just what
they are. See the [architecture](architecture.md) document for details on how the firewall
integration is implemented.

The main purpose of the app is to allow the user to make all network/internet traffic to and
from the device travel via an encrypted VPN tunnel.

## Desktop vs mobile

For desktop operating systems, the security is ensured via tight integration with the default
system firewall. This means WFP on Windows, PF on macOS and nftables on Linux. All changes to
the rules are applied as atomic transactions. This means that there is no time window of
inconsistent or invalid rules during changes.

This file has been truncated. show original

I glanced this document and I noticed there is this setting called Allow LAN.
By enabling this, MullvadVPN should not affect the 10.0.0.0/8 IP range (used by Incus).
Can you check whether that is a good workaround for you?