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.

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

Changes to remote's and DNS firewall rules #167

Merged
merged 2 commits into from
Jul 2, 2022
Merged

Conversation

ak-1
Copy link
Contributor

@ak-1 ak-1 commented Jul 1, 2022

This is related to #162 and #163. It is the firewall setup that I am using without any issues (with OpenVPN and IPv4 only). There is no new code as you can see. I only enabled/removed existing code. I have no idea if this would also work in general though. Maybe this shouldn't be hard coded, but controlled by options or other logic instead.

@jamesmcm
Copy link
Owner

jamesmcm commented Jul 2, 2022

Thanks it works well for Mullvad and ProtonVPN.

My only concern would be for OpenVPN providers that don't provide a DNS server internal to the VPN connection and the OpenVPN hosts are given as domain names not IP addresses - so it'd need to connect to the DNS server first when creating the OpenVPN connection.

But even PIA provides the DNS servers internally too now so I don't think it's a problem. And the killswitch is run after the connection is established so it should be okay, I''m sure I had some issue around this during implementation before though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants