-
Notifications
You must be signed in to change notification settings - Fork 198
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
[Enhancement] Allow multicast DNS on local interfaces in killswitch mode 2 #247
Comments
Floppy
changed the title
[Enhancement] Allow mulitcast DNS on local interfaces in killswitch mode 2
[Enhancement] Allow multicast DNS on local interfaces in killswitch mode 2
Oct 19, 2020
It actually only needs UDP on one port:
|
Floppy
added a commit
to Floppy/linux-cli
that referenced
this issue
Oct 19, 2020
So that we can still use mDNS hostnames for devices on the local network when the killswitch is enabled. Resolves Rafficer#247.
Floppy
referenced
this issue
in Floppy/linux-cli
Jun 26, 2021
So that we can still use mDNS hostnames for devices on the local network when the killswitch is enabled. Resolves ProtonVPN#247.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The killswitch iptables config filters out multicast DNS, so hosts aren't accessible via mDNS names on local networks; i.e. I can't ssh to my machine running the VPN by name, only by IP.
Expected behavior
Multicast DNS should be allowed on the default interface as well as local network access.
Possible solution
I think the right solution is to add the mDNS IP
224.0.0.251
as a rule the same as the local network specifier athttps://github.com/ProtonVPN/linux-cli/blob/1190545a4293332824b28fe442f95f7be44b65d5/protonvpn_cli/connection.py#L849. I'll have a go and send a PR.
Concerns
I'm not sure what the security implications are of doing this... any thoughts?
The text was updated successfully, but these errors were encountered: