Deny VPN accessing applications extra open ports #26
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This denies incoming_ports_ext_array and incoming_ports_lan_array from being accessed form the VPN.
This was referenced Aug 24, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request denies
incoming_ports_ext_arrayandincoming_ports_lan_arrayfrom being accessed from the VPN. The idea is those should only be accessible from the LAN/host or the docker network.Originally I had made a pull request on binhex/arch-delugevpn for this, but you have since moved it to this repo.
The custom VPN I am using seems to forward most/all ports automatically (they're dedicated IP addresses it seems). This is great, however it allows for the web ui and the daemon port (in Deluge) to also be accessible to the VPN network. A user could find my current VPN IP address (from the swarm, or just port scanning random IP addresses) and access either of those services. Granted, they are password protected, but it would be nice to have these ports closed/drop in the IP tables setup.
Not sure if there is a better/more secure way of solving this; all I know is that without this modification, I can see both ports 8112 and 58846 open when I use a port scanner on my VPNs IP address. When I use this modification, they are no longer open.