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

Near-Path NAT: Performance and trust issues #11

Open
jimaek opened this issue May 4, 2022 · 1 comment
Open

Near-Path NAT: Performance and trust issues #11

jimaek opened this issue May 4, 2022 · 1 comment

Comments

@jimaek
Copy link

jimaek commented May 4, 2022

Hey, it's not really clear how the proposal will solve the following issues:

  1. Performance - It will add a minimum of 1 extra hop, and additionally it could create issues on the routing level. If the extra hop privacy proxy doesn't peer with the CDN and the user's ISP the latency would suffer
  2. Trust - The NAT will have too much power to monitor, filter and censor traffic that flows through it

It would be nice to try and consider these issues

@bozicm
Copy link

bozicm commented Oct 5, 2022

I would add No. 3: NP-NAT would another layer to troubleshooting the network issues and would actually contribute to disabling NP-NAT indefinitely (e.g. "Having network issues? Disable the firewall!"), thus defeating the purpose of such solution. For example, I use an ad blocker, but then some sites have implemented detection of ad blockers and won't display their content if I don't disable it.

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

No branches or pull requests

2 participants