Network interface names differ between sys-net and its disposable template

[p1llule]

How to file a helpful issue

Qubes OS release

4.1

Brief summary

Due to interface naming differences between the template of the disporable vm and the disposable vm, the files in /rw/config/NM-system-connections may not be correct for disposable vms.

Steps to reproduce

Stop sys-net.
Connect wifi PCI to the template of disposable sys-net.
Register connections on the template of disposable sys-net.
Stop the template of disposable sys-net.
Start sys-net.

Expected behavior

Connection UP
The files in /rw/config/NM-system-connections are still correct.

Actual behavior

Connection DOWN
The files in /rw/config/NM-system-connections refer to the wifi interface of the template of disposable sys-net, which is not named the same way for sys-net (eg: wls6 and wls7).

Related issues

#7284

[p1llule]

workarounds:
or Edit the connection to suppress the interface-name configuration in the disposable template (use nmcli or nmtui, the file itself may be erased by the daemon).

or change the process :

1. connect the disposable VM to your wifi
2. copy the connection files to its disposable template
3. profit.

[ghost]

Perhaps a better title would be: "Interface names differ on dispVM from templateVM"

[andrewdavidwong]

Perhaps a better title would be: "Interface names differ on dispVM from templateVM"

This is referring to a disposable template, which is not the same thing as a template (previously known as a "TemplateVM").

[p1llule]

thx adw,

Reading a bit more about this on the forum, it seems most people have already found a good workaround (connecting in the disposable and then copying connection files to the disposable template).

Or maybe plugging another VM with a password manager somehow.

Tbh I think theses solutions are better than what I was relying on before, so I am merely documenting the issue if anyone was in the same case as me and asking to close the bug as wont fix.

[andrewdavidwong]

A workaround is not a fix, though, and users shouldn't have to find this issue just to get their networking to work when it ought to work out-of-the-box. Maybe I'm misunderstanding you, but it sounds like there might still be a bug here that'd be worth fixing.

[github-actions]

This issue is being closed because:

• This issue is believed to affect only Qubes OS 4.1 (and possibly earlier).
• Qubes OS 4.1 has reached end-of-life (EOL).

If anyone believes that this issue should be reopened, please leave a comment saying so.
(For example, if a bug still affects Qubes OS 4.2, then the comment "Affects 4.2" will suffice.)