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

Remove Carrier-grade NAT ranges #106

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

PoneyClairDeLune
Copy link

@PoneyClairDeLune PoneyClairDeLune commented Nov 20, 2024

The 100.64.0.0/10 range is a shared address space used by service providers to provide carrier-grade NAT services, according to the exact article where this list is suspected to be copied from, which should not be considered as "private" when it's never used "privately" and the service provider can have legit uses with its subnets. One of its subnets would be a great candidate for use with FakeDNS, as if it's not routed on the client, the server can handle that as well per its original designation, allowing server-side FakeDNS.

Server-side FakeDNS has the following uses:

  • Permit access to endpoints that will never realistically have an associated IP address, e.g. Onion services (.onion) and Eepsites (.i2p).
  • Offer an effective alternative to NAT64 (and NAT46), where the client is no longer required to communicate with the service on a stack it's only available on, like IPv4 clients to IPv6-only servers and vice versa.

All the uses listed above have already been proven achievable with standard V2Ray/Xray config files, and has a userbase that offers varying levels of legit interest not affiliated with any commercial incentive.

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.

1 participant