Strengthen current capability to connect across different networks

[lammel-hub]

Is your feature request related to a problem? Please describe.
When stresstested, Dayon! has challenges to get through some Corporate Grade NATs and firewalls, as discussed in issue #178

Describe the solution you'd like

• An improved capability of the Assistant to establish contact with the Assisted.
• The intention is not to affect the fundamental model of the Assisted actively requesting help from the Assistant, but rather to increase their chances of being able to connect.
• I believe the rvs would still play the same role as today, but perhaps with some adjustments to the script.

Describe alternatives you've considered
Using lanproxy or UDP Hole Punching to implement this: both are available and available in java with open source licensing (please refer to issue #178 for the full discussion, including links).

Additional context
Hoping this is an easier iteration to implement, rather than wait and include it as part of unattended access (currently postponed)

[RetGal]

I'll address this issue, but I'll would like to avoid operating an external server infrastructure for this at all costs.

For this reason, the network traffic has to remain remain peer to peer. (Except for the initial query of the peers to the Rendezvous/Token server)

I'm currently experimenting with TCP hole punching, which will very likely be the way to go - once I've got it working reliably, of course.

To summarize all this: The feature will definitely be implemented before #178, but I can't make any predictions about the time frame at the moment.

[lammel-hub]

I fully agree that keeping the p2p model is essential.

Likewise, I am excited that you have already started experimening, and that you share my sentiment to make this a first step.

Looking forward to your progress on this, regardless of timeline 👍