-
Notifications
You must be signed in to change notification settings - Fork 122
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
hole punching alternative #130
Comments
You can check this example |
I tested it a few weeks ago, but throws me a NullPointerException at line 43, when it sends a message from "unreachable1" to "unreachable2". I don't know if is a library problem or my dev environment. However, thanks for your help! |
Any progress on this? |
Still no answer from main developers :-/ |
Sorry for the delay, we are working on https://github.com/jonaswagner/sctp4j, which will make hole punching much easier. The idea is to have SCTP tunneling over UDP. That means if we have a UDP connection we can "upgrade" to SCTP. That also means we will ditch TCP and use UDP and SCTP only. |
I have read in your webpage that the latest release of TomP2P does not support hole punching. I would like to know if TomP2P has any alternative to send direct messages between to peers in different networks, that is, between NAT-ed LAN networks, either implemented in the library or planned to be in the future. If it exists, is there any example available?
The text was updated successfully, but these errors were encountered: