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

Include 100.64.0.0/10 in ALLOWED_LAN_NETS #6089

Closed
wants to merge 2 commits into from

Conversation

chaeynz
Copy link

@chaeynz chaeynz commented Apr 8, 2024

I added the 100.64.0.0/10 address space to ALLOWED_LAN_NETS.

100.64.0.0/10 is reserved by IANA as Shared Address Space, is filtered on the public Internet through routing filters (May not be advertised) and can therefore be treated as local.
https://datatracker.ietf.org/doc/html/rfc6598

It mainly serves ISPs, but can also be used on the internal network by organizations of any kind.

Please merge my PR, so that users will be able to access parts of their network where this address space is used, while still being connected to the Mullvad VPN.

Closes #6086


This change is Reviewable

@chaeynz chaeynz changed the title Patch 1 Include 100.64.0.0/10 in ALLOWED_LAN_NETS Apr 9, 2024
@0xBA5E64
Copy link

0xBA5E64 commented May 7, 2024

Really hoping to see this get merged! Mullvad's lack of interoperability with Tailscale is particularly frustrating since the two projects do already have interoperability though Mullvad exit nodes on Tailscale.

However, as an ordinary Mullvad user however, I really hope to be able to use something like this instead.

@faern
Copy link
Member

faern commented Aug 28, 2024

I'm not comfortable just calling this network a "LAN" and blindly allow it for everyone who wants local network traffic. This network is primarily intended for CGN. This would be a risk to most customers, and a benefit to probably very few.

If you run Linux, you can apply custom Firewall rules and allow 100.64.0.0/10 by yourself. See this guide: https://mullvad.net/en/help/split-tunneling-with-linux-advanced

Maybe we should consider adding a feature where the user can enter a list of networks that they want unblocked?

@faern faern closed this Aug 28, 2024
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.

100.64.0.0/10 is not included in allowed LAN ranges
3 participants