/qubes-issues

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apply fw rules for templateVMs as well #167

Closed
marmarek opened this Issue Mar 8, 2015 · 5 comments

Comments

Assignees

@marmarek marmarek

Labels
Projects
None yet
Milestone
  Release 1 Beta 1
2 participants
@marmarek @rootkovska
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by joanna on 30 Mar 2011 08:34 UTC
It makes perfect sense to limit the TemplateVM to e.g. only downloads.fedoraproject.org. I assume there is no reason why shouldn't we allow for that, right? (i.e. it doesn't complicate anything)/

Migrated-From: https://wiki.qubes-os.org/ticket/167

@marmarek marmarek assigned rootkovska Mar 8, 2015

@marmarek marmarek added this to the Release 1 Beta 1 milestone Mar 8, 2015

@marmarek marmarek added bug P: major labels Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 30 Mar 2011 08:50 UTC
Also, for some reason when I start a templatevm no firewallruls (even the default ones) are added in the firewallvm. This makes networking not available in templatevm, which is bad (updates/new sofwtare installation).
Member

marmarek commented Mar 8, 2015

Comment by joanna on 30 Mar 2011 08:50 UTC
Also, for some reason when I start a templatevm no firewallruls (even the default ones) are added in the firewallvm. This makes networking not available in templatevm, which is bad (updates/new sofwtare installation).

@marmarek marmarek added C: core P: critical and removed P: major labels Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by smoku on 31 Mar 2011 14:32 UTC
Replying to joanna:

Also, for some reason when I start a templatevm no firewallruls (even the default ones) are added in the firewallvm. This makes networking not available in templatevm, which is bad (updates/new sofwtare installation).

It's an issue with VM class hierarchy - firewall rules are generated for AppVMs only (vm.is_appvm()) and TemplateVM is not AppVM.
Member

marmarek commented Mar 8, 2015

Comment by smoku on 31 Mar 2011 14:32 UTC
Replying to joanna:

Also, for some reason when I start a templatevm no firewallruls (even the default ones) are added in the firewallvm. This makes networking not available in templatevm, which is bad (updates/new sofwtare installation).

It's an issue with VM class hierarchy - firewall rules are generated for AppVMs only (vm.is_appvm()) and TemplateVM is not AppVM.
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 31 Mar 2011 14:33 UTC
Member

marmarek commented Mar 8, 2015

Modified by joanna on 31 Mar 2011 14:33 UTC

@marmarek marmarek assigned marmarek and unassigned rootkovska Mar 8, 2015

@marmarek marmarek changed the title from Allow to edit fw rules for templateVMs as well to Apply fw rules for templateVMs as well Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by marmarek on 31 Mar 2011 19:03 UTC
Member

marmarek commented Mar 8, 2015

Modified by marmarek on 31 Mar 2011 19:03 UTC
@marmarek

@marmarek marmarek closed this Mar 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment