Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Blocking connection to a specific IP #122

Open
BlueTree242 opened this issue Jun 12, 2024 · 0 comments
Open

Blocking connection to a specific IP #122

BlueTree242 opened this issue Jun 12, 2024 · 0 comments

Comments

@BlueTree242
Copy link

The server has an additional IP address from the hosting provider. I already added all the rules normally. However currently the second IP can be used to connect to docker services. Adding a rule to block without "route" to the secondary address blocks things outside of docker like ssh, but with "route" it does not work. It's like either both or none. Does anyone have a solution or at least have an explanation?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BlueTree242