GNOME Bugzilla – Bug 730789
Allow disabling network in VMs
Last modified: 2018-01-11 10:08:29 UTC
I noticed that currently Boxes doesn't have the possibility to unshare the network connection. Since VMs are sometimes intentionaly encapsulated from the environment around them we should allow that. The primary usecase is the usage of untrusted programs within a trusted network via a VM.
(In reply to comment #0) > I noticed that currently Boxes doesn't have the possibility to unshare the > network connection. > > Since VMs are sometimes intentionaly encapsulated from the environment around > them we should allow that. > > The primary usecase is the usage of untrusted programs within a trusted network > via a VM. The network *is* separated from the physical environment since its essentially NAT.
I think this is about totally disabling networking in the VM.
(In reply to comment #2) > I think this is about totally disabling networking in the VM. Yes, thats what I meant.
(In reply to comment #3) > (In reply to comment #2) > > I think this is about totally disabling networking in the VM. > > Yes, thats what I meant. OK, thats different then. :)
Makes sense Jimmac?
Exposing the IP in the properties as you described it on IRC makes sense. Not sure about the provided use case for disabling network access. I guess this is to simulate the equivalent of "yanking the cable" for testing purposes, just really making sure the box has no network access... I'd be looking for this in the properties/system.
(In reply to Jakub Steiner from comment #6) > Exposing the IP in the properties as you described it on IRC makes sense. > Not sure about the provided use case for disabling network access. I guess > this is to simulate the equivalent of "yanking the cable" for testing > purposes, just really making sure the box has no network access... Yeah, shouldn't be hard and shouldn't clutter the UI so I'd implement this and bug#744004 together. Just for the record here, my idea is adding this under System tab of properties: Network [toggle] IP: x.x.x.x
(In reply to Zeeshan Ali (Khattak) from comment #7) > (In reply to Jakub Steiner from comment #6) > > Exposing the IP in the properties as you described it on IRC makes sense. > > Not sure about the provided use case for disabling network access. I guess > > this is to simulate the equivalent of "yanking the cable" for testing > > purposes, just really making sure the box has no network access... > > Yeah, shouldn't be hard and shouldn't clutter the UI so I'd implement this > and bug#744004 together. Just for the record here, my idea is adding this > under System tab of properties: > > Network [toggle] IP: x.x.x.x Tried this and failed to make it look good. Also thought more about it and discussed here with David King. The thing is that this can easily be done from within guest (e.g ifconfig eth0 down) so there is no compelling reason for us to provide this from outside the guest. So closing this as INVALID.
*** Bug 754236 has been marked as a duplicate of this bug. ***
*** Bug 780803 has been marked as a duplicate of this bug. ***
Don't remember when and why this was marked as INVALID but I don't see anything in the latest comments about not wanting to do this.
I second this. Target Milestone is 3.22, but I can confirm that v3.22 does not have this feature. This is an essential (& basic) feature for VMs, so please support it.
(In reply to 1d28ed33 from comment #12) > I second this. Target Milestone is 3.22, but I can confirm that v3.22 does > not have this feature. If only one can meet targets. This is not marked as "FIXED". > This is an essential (& basic) feature for VMs, so > please support it. Sure but keep in mind that Boxes team currently consists of only 1 dev who has other responsibilities too.
Oh, okay. Then maybe ramp up the milestone, to show in which version we can expect this feature.
(In reply to 1d28ed33 from comment #14) > Oh, okay. Then maybe ramp up the milestone, to show in which version we can > expect this feature. With the team so slim, you can't plan too far ahead and you'll just end up bumping the milestone after every release for most feature requests.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-boxes/issues/25.