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
Carrier-grade NAT may affect the stability of websocket connections #441
Comments
@danielsz Thanks Daniel, much appreciated! 🙏 I'll do some digging into this the next time I'm on batched Sente work. In the meantime, I'd like to please ask anyone else that may have experienced something similar to 👍 and/or share extra details if they have any. Thanks! |
@danielsz One question so long: when you observed the flaky WebSocket behaviour - was it actually in the context of Sente, or elsewhere? |
Yes, in the context of Sente, developing a project. The crucial part I don't remember is if it was all websocket connections or just my developer environment which was behind a tunnel. |
Carrier-grade NAT is a practice by ISPs that allows them to share small pools of public addresses among many end users. I believe that in certain circumstances, carrier-grade NAT may affect the stability of webcocket connections, possibly in non-trivial developer setups or otherwise. Some time ago, I was observing constant interruptions of websocket connections. I called my ISP and they told me that they were aware of the problem, explained it was due to carrier-grade NAT, and upgraded my subscription. No more carrier-grade NAT, now I get assigned a public IP address that is not shared (still dynamic though), and that was the end of the problem.
Unfortunately, I am fuzzy about the details since that was some time ago.
The text was updated successfully, but these errors were encountered: