>> O_o tell us what this magic works on? >> if you are behind the nat, then ntcp will not work, and if you do not >> forward the port, then ssu will not work either. all kinds of manuals talk >> about this. i'm watching on it right now. >> if you have found a solution, then all of humanity will be grateful to you ;) > I'm sorry to disappoint you, and even more all of humanity, but I didn't do > anything magic, except perhaps disabling UPnP on my ISP's router. It just > happens to work for me. to begin with, you should understand how it works. for example, how the mailing list works ;) in it a letter comes only to those who are specified in the headers To, CC, BCC. others can see it if they receive all letters in this mailing list and they view each message. of course, not everyone does this. for example, i am informed only about letters that are addressed among others to me. how else if there are dozens of letters in a day? therefore, if you want to be guaranteed to be heard, then do not forget to fill in the headers correctly.
you're right, it works for nat without port forwarding(although in fact there is a forwarding but it's not permanent). but this is a scheme with an intermediary with whom the client behind nat keeps in touch constantly, and when someone wants to establish a connection with the client behind nat, he first contacts the intermediary(it should have a white address), and the intermediary informs the client behind nat that somebody want to establish a connection with him from such ip, and already the client behind nat addresses via udp to this ip, thereby punching a hole in nat, through which it is already possible to connect with the client behind nat directly. but in general, this scheme is not working, since there are no analogues of the intermediary from i2p in internet
