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

Qubes Manager/ Firewall: Allow rules for ports #961

Closed
nvesely opened this Issue Apr 25, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@nvesely

nvesely commented Apr 25, 2015

It would be nice to have the ability to only allow traffic to flow through certain ports from the Qubes Firewall menu. Rules could be a combination of port + (domain or ip address (range))--while either side of the + could be a wildcard.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Apr 25, 2015

Member

I'm assigning milestone 3.1 for now, but in practice I think it would be much easier to implement it in Qubes 4.x (so not this year...), because current firewall rules generator (and config format) is really limited and will be rewritten in Qubes 4.0 anyway.

Member

marmarek commented Apr 25, 2015

I'm assigning milestone 3.1 for now, but in practice I think it would be much easier to implement it in Qubes 4.x (so not this year...), because current firewall rules generator (and config format) is really limited and will be rewritten in Qubes 4.0 anyway.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 8, 2016

Member

I've read your description again. It is exactly how firewall rules are working there. You can use * in address field (which is one of examples in drop down menu there).

Member

marmarek commented Feb 8, 2016

I've read your description again. It is exactly how firewall rules are working there. You can use * in address field (which is one of examples in drop down menu there).

@marmarek marmarek closed this Feb 8, 2016

@marmarek marmarek added the notanissue label Feb 8, 2016

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