Why when Vault Cube is switched to Debian does it show an IP Address?
I have tried also cloning Vault Cube then switching the clone to Debian yet an IP Address is shown for the clone Vault even though all the settings are None i.e. no Internet and in firewall it even says no internet in red but still an IP Address is shown in Qubes manager under the cloned vault yet not if the said vault VM is on Fedora?
I wanted a Vault VM Cube where i can plug in all my USB Files and work on them using Libre Office yet Libre Office is only in Debian and not Fedora which is also confusing too but i just thought i could simply switch to Debian but im scared about this IP address showing as i dont want my external SSD Cube to have an IP Address.
Can you share the whole output of the command ip address please?
Are you sure the qube has no network VM? If no network VM are set, reboot the qube to be sure. (removing its network VM will not remove the network interface until a reboot happens)
This behavior has me curious. My vault VM is already debian and has no internal ip address, but if I simply switch the template to fedora an internal ip of 10.137.0.x is provided. So that’s a confirmation of the behavior. Nevertheless, ip a displays only the loopback interface, so there is no outside connection.
Even though it already shows as “none”, manually selecting none as the network vm removes the internal ip for the qube. Triggering an internal ip address by simply changing the template seems undersirable for any qube without a network vm. Anyone have an idea of the cause?
What do you mean by “an internal IP is provided”? Where do you see this?
AFAIK every qube is allocated an IP address on creation, but it is
normally only exposed when a netvm is allocated.
I cant replicate this when changing templates so it would be good to
know where you see the allocated address. I dont see it under qvm-ls -n or in Qube Manager.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
i am just looking at the Qube Manager (Not Terminal) and under IP it states which Qubes have what assigned IP addresses if that helps?
I also shut it down and re-started it but same.
please open up Qube Manager and only use the GUI rather than Terminal when trying to replicate the issue as thats where the issue is seen if your not doing that already of course, then look directly under the IP where it states all Qubes with IP Addresses, then this is where i see the said address and i think the other person too, i presume they right click on a said Qube and switch the said template yet for some freak reason its not doing it for me right now, maybe i have gone insane.
I’m able to observe the addition of a 10.137.0.x address in the IP column of the Qubes Manager after right-clicking to change the template, or after cloning, a non-networked VM for which the IP entry was previously blank. However, if I open a new instance of Qubes Manager the ip address is once again blank. qvm-ls -n has not listed an ip address for the qube in either case, nor has the provides network box been ticked under settings.
I replicated with both qubes-manager 4.2.8-1 and 4.1.31-1. Here is a snapshot of the behavior in Qubes Manager and the results of qvm-ls -n, followed by opening a new Qubes Manager, where the IPs no longer appear.
right-click > template from Qubes Manager led to the above behavior, right-click > settings > template did not, but that’s not all. Once I had changed the template using the latter method, I could no longer replicate the behavior with the former method (IP now remains blank). However, right-click > Clone qube continues to add an IP.
I’m not on GitHub and avoid all things Microsoft. I could not find a similar report in qubes-issues so I went ahead and wrote up a report based on the old issues template. I hope that might lesson the effort if someone who is on GitHub wants to post the issue:
qubes-manager reveals IP address of a non-networked vm
qubes-manager reveals IP address of a non-networked vm
(minor cosmetic bug)
Qubes OS version:
4.2.2 (R4.2)
Affected component(s) or functionality:
qubes-manager 4.2.8-1 reveals IP address of a non-networked vm
Steps to reproduce the behavior:
Completing either one of two separate actions in the Qubes Manager GUI will reveal the IP address:
Right-click → Clone, or
Right-click → Template
Expected or desired behavior:
A cloned, non-networked, vm (e.g., the vault qube) will not display an IP address (10.137.0.x) in the Qubes Manager. Likewise for a non-networked qube with a new template.
Actual behavior:
The IP address of the non-networked qube is displayed in the GUI. However, there is no IP address listed after qvm-ls -n, nor is there a networked interface created within the qube (only the lo interface).
If one changes the template in the GUI via Right-click → Settings → Template, then future modifications via Right-click → Template will no longer reveal the IP.
General notes:
Appears to be a minor, cosmetic, bug since the GUI only suggests that the qube is networked when it remains, in fact, non-networked.
I am aware of the following related, [non-duplicate] issues:
