Connection metadata
Opened this issue · 1 comments
We should expose more metadata about connections, ie.
remoteIp
holepunchStrategy
isLocalNetwork
connectionType, utp, udx, tcp etc
etc, we might already expose some and if so document how to access it
Thanks @mafintosh this will half the latency of my dynamic DNS server
Would it be beneficial to be able to do the ip/network/holepunch part without actually completing a connection? So that computers can discover each other's ip and find out if they're on the same network and some NAT details about how they discovered each other, but without actually setting up a noise stream
I also really like the idea of reporting on lan detections,
Does this imply that hyper can operate on LANs that are offline? I am really interested in using it for local file copies for large datasets (I manage 1.5tb/1 million files)