Firewall rules about terry-the-terraformer HOT 4 CLOSED

After looking further, it is going to be very difficult to implement IP and port. Implementing the IP is easy, but there are some flaws with port as I will need to have it taken in as a CLI param since the redirectors can map to any non-standard port to transfer C2 comms over Nebula / internet.... still working on it though

from terry-the-terraformer.

I didn't use that branch, but changes have been pushed to address this, it now has a "blanket" approve for all firewall rules across the cluster. So all resources can freely communicate with each other over the internet (not great, but best I can do given ports may differ if you use containers)

from terry-the-terraformer.

I thought you told me this only worked with Nebula.

from terry-the-terraformer.

As it worked in the past, yes, but I was able to make it work as long as all of your resources are routable directly from the internet. Also, there’s no granular control of allowed ports in the solution I committed, it’s allow all from all resources in a build

from terry-the-terraformer.