* Package name : pwnat Version : 0.3 Upstream Author : Samy Kamkar <samy@samy.pl> * URL : https://samy.pl/pwnat/ * License : GPL Programming Lang: C Description : allows clients behind NATs to communicate Pronounced "poe-nat", a tool that allows any number of clients behind NATs to communicate with a server behind a separate NAT with *no* port forwarding *no* DMZ setup, and *no* 3rd party involvement. The server does not need to know anything about the clients trying to connect. The same author wrote a similar tool, chownat https://samy.pl/chownat/ , which might make sense for whomever packages this to also package.
I have reviewed the packaging of Nilson Silva <nilsonfsilva@hotmail.com> but it got blocked as I'm not sure this package is a good fit for our official repos. I could find issues on upstream's Github where people are talking about how the method pwnat uses is outdated (upstream even wrote a replacement, called slipstream)[0]. pwnat doesn't work with new routers (as of at least 2017), it might not work with CGNAT, and it relies on the fact that the IP address 3.3.3.3 is unreachable (I'm not sure if a host on 3.3.3.3 would break pwnat or not, but ISPs might be blocking this too now). Some links for those issues: https://github.com/samyk/pwnat/issues/18#issuecomment-703373953 https://github.com/samyk/pwnat/issues/17#issue-619482494 https://github.com/samyk/pwnat/issues/10#issuecomment-282223632 Since I didn't went all the way into the rabbit hole when doing my analysis, I could be wrong and in fact pwnat will work in most of the cases, if that's the case, please reply to this bug with details. Thanks, [0] https://github.com/samyk/slipstream