Broken firewall rules for GCE about inletsctl HOT 6 CLOSED

@alexellis The ports 80 are opened by using the http-server target tag for the exit node while provisioning. Every project comes with some default firewall-rules

from inletsctl.

I just ran through this, and my screenshot shows that the port 80 was closed and not opened. I had to edit the firewall rule in the GCP console to access it.

from inletsctl.

This is what I got for inlets-pro, a firewall with the wrong port again, it should have at least 8123 for the control-port for auto-tls and then * open for any port the user decides to punch out via the client.

It's impossible to set a restrictive port range for inlets-pro since the client decides which ports to open.

from inletsctl.

@adamjohnson01 does this apply at all to the EC2 provisioner? I think only GCE + EC2 have security group / firewall config added.

from inletsctl.

Also broken in the operator -> inlets/inlets-operator#46

from inletsctl.

This should fix all the problems #58
cc @alexellis
cc @burtonr

from inletsctl.