How to set the template of sys-net to debian-minimal?

[ckN6QwSZ]

@enmus

Store these in its dvm-template’s /rw/config/NM-system-connections/ and you’re good to go with disposable wifi too.

Interesting idea.

@enmus

I’m even more extreme. I have one dvm-template per connection with only one wifi firmware per dvm template, meaning I’m not connecting to the same wifis with different devices.

Hmmm, I was actually about to go the opposite way. Using the same dvm-template for sys-net and sys-wifi, store all nmconnections in there but attach different PCI-devices to them.

The only threat I can infere is an information leak. A pawned sys-wifi (or sys-net using the same dvm-template) enables an attacker to see which network-devices your machine posesses and to which wifis you have been connected to.

PS: okay, I see, that might not be a minor issue since the BSSIDs could be used to uncover your geographical location…

PPS: on the other hand as sys-net/wifi would be attacked from the local net an attacker already has your geographical location.

[enmus]

Hahah, you made my day.
Well, I have more. One “disposable” cheap dongle per abroad travel, bought there.

[ckN6QwSZ]

@enmus

One “disposable” cheap dongle per abroad travel, bought there.

Ok, but what is your threat model here?

Or is this about wifi-frequencies?

[Euwiiwueir]

@tanky0u

Now install the necessary packages for network management:
(in dom0) $ qvm-run --pass-io -u root deb11min-net "apt install --no-install-recommends -y firmware-iwlwifi qubes-core-agent-networking qubes-core-agent-network-manager"

For posterity: beginning from a debian-12-minimal, in addition to these packages I needed wpasupplicant. (Context)

[thimbles_taxidermist]

how do I do that?
Do I have to follow this guide: Disposable sys-net: Automatically connect wifi (config file or RPC service)
or is there something simpler?

[Timewulf]

I’ve often searched similar tasks.

Look here, I’ve put my own Step-by-Step Guide online.

Guide to build a "sys-mini" template for all service-qubes

Idea Any updates or changes to the template of your service qubes imply the risk of a hidden error, making your service qubes unbootable. A separate template / disposable template only for service qubes should decrease this thread. Having one complete step-by-step guide to save much time for seeking the not mentioned details … There are a few guides around this theme complex, but none of them is covering all aspects, so one has to jump between multiple sources. Thoughts Building a separate te…

The guide you’ve mentioned is the last (optional) step for convenience.

[parulin]

@thimbles_taxidermist

or is there something simpler?

Yes, just follow the original advice, copy /rw/config/NM-system-connections to the disposable template See the solution of this topic:

NetworkManager not using nmconnection file

Hello, I am fairly new to Linux so the solution is probably pretty basic, but I could not find anything concerning this anywhere. I was trying to make my WIFI persistent inside my disposable sys-net qube by copying the nmconnection file to the /rw/config/NM-system-connections directory of my fedora-dvm template qube. For context I tried copying it 2 different ways by using the qvm-copy-to-vm copy function of qubes by creating the file with nano and copying the contents and I ran into the s…