-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Firewall rules #8
Comments
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 |
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) |
I thought you told me this only worked with Nebula. |
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 |
If Nebula is not being used, suggest the following:
The text was updated successfully, but these errors were encountered: