Logan oos Even

First thing to do is to add a network connection layer. It will help us to take care of UDP and TCP at the same time and switching to TCP...

> So what’s the next step? 1. network connection layer (to deal with different/multiple sockets) 2. auto switch TCP / UDP 3. uPnP (if somebody implements it) 4. parallel connection...

> more people should be involved. More volunteers and contributions always are very welcome! > I am concerned that there will be compatibility issues by that date The 3.x series...

> Fengdaolong has promised to add upnp ... Great news! > ...before releasing n2n_v3. > He’s worried he won’t be able to keep up with n2n_v3. No worries! If it...

> a lot of people are still using early versions I assume a major reason being the fact that 2.9 is the _development_ version with a high frequency of (compatibility...

> I think there should be a news, ... psp; > psp to p2p Actually, this message already is in the code (`src/edge_utils.c:816`). It will only be output at higher...

> And the version of supernode. #894

The version number is not transmitted in REGISTER_SUPER_ACK but in PONG message. Hence, it cannot be displayed with this message which occurs on the very first REGISTER_SUPER_ACK.

Maybe an additional federated supernode could do instead then? The idea of "nodes without virtual TAP" will not become reality before 4.0 for which we plan all equal nodes, some...

Generally speaking, I believe that everything is possible… :wink: tcp hole punching would as a prerequisite require to implement tcp in a first step, see [here](https://github.com/ntop/n2n/issues/353#issuecomment-670100395). And then, for the...