3 ms·
> because some nodes are behind restrictive firewalls and NATs That is just a weird turn of phrase on my part, will fix it. What I mean is: because some nodes
by rolleiflex 8y ago
> because some nodes are behind restrictive firewalls and NATs
That is just a weird turn of phrase on my part, will fix it. What I mean is:
because some nodes are behind restrictive firewalls and [restrictive] NATs.
In other words, most NATs work fine. Even if they don’t work fine, it has a process called a ‘reverse open’ where the inbound connection is requested by the receiving remote and the remote ‘captures’ and uses the same TCP socket.
Even if that doesn’t work, as you’ve discovered, you can run the backend Ona VPS.
- tomsmeding 8y agoThanks for replying -- the client seems to work beautifully on osx here. It took some time to start showing post content, and I even restarted it once because it didn't seem to do that after a few minutes, but now it does, so that's good. My NAT is apparently a restrictive one, since I've got "Mapping failed, no router, or router uncooperative" as my port mapping status. But as you predicted, I've indeed got some inbound connections, so yay.
- Orochikaku 8y agoI unfortunately am getting the same error however I'm not getting any inbound connections either https://i.imgur.com/49VaP62.png https://i.imgur.com/49VaP62.png
- ithrewthat4351 8y agoTIL what reverse open is; nifty.