Missing Qubes OS Documentation

Feedback Website Feedback
1

Hello.

I have created a standalone EndeavourOS Qube, with the networking set up properly. However I had problems with the documentation. I found this, but I feel it is missing a section.

Under the heading “Setting up networking for HVMs” it shows the Qube settings, IP address, gateway, etc. However, it stops abruptly without explaining how to transfer the data to KDE’s Network Manager, or whatever is being used in the guest operating system.

I think that this section would be much more useful if the missing section was added.

Can the missing section be added? Can I add it?

4 Likes
2

Yes:

4 Likes
3

Thanks for the offer to help.
I’m not sure that the information is “missing” since the solution will
depend on what OS is being installed. A generic explanation that you
should use that information to configure the OS in the native way could
be added. Perhaps with an example?

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

1 Like
4

My personal example was EndeavourOS, with KDE and Network Manager. So I thought that an example like Network Manager in KDE would be a good place to start. Your idea of a generic explanation is a good one, we can deal there, amongst other things, with the netmask issue (Qubes says 255.255.255.255, my network needs 255.255.255.0). I could also create a standalone VM with a Gnome or XFCE desktop, and have multiple examples. That would be four sections, with text and images. We can add other operating systems as seems necessary (Arch? Windows?)

Sorting out the network for a standalone VM is a major pain point at the moment, but once the user understands what is required then it becomes, I think, reasonably easy. Potentially, then, a quick win.

1 Like
5

I’d prefer NOT to have multiple examples. Network Manager is reasonably
widespread. Windows and Android have their own approaches. But generally
I think that someone who wants to do this would be able to look to see
how to configure the network in their chosen OS, and we dont want to
duplicate that information.
I suggest making it clear what information needs to be input, point
user to make use of guides for their situation, and provide one example.
Let’s see what that look like.
Thanks again

I never presume to speak for the Qubes team. When I comment in the Forum I speak for myself.
2 Likes
6

I have made the changes and done a pull request.

I have two images to add, although I don’t know how to do that, and I have left marker points for their later insertion.

2 Likes
7

I never tried it, but you have another qubes-attachments repo for this:

1 Like