Open marten-seemann opened 1 year ago
Should we just focus on autonat v2?
Makes sense. Having this tested end-to-end (with "real" NATs) is valuable, even if rust-libp2p and js-libp2p don't have an implementation right away.
No significant users of AutoNat in rust-libp2p, js-libp2p has this feature but unsure of users. Although only one implementation will have v2 (go-libp2p), it will still be valuable to add as an interop test as it's difficult to test in unit tests
What is the progress on the V2 spec and the go implementation? I am interested in having V2 asap in rust-libp2p
because with our recent release of kademlia client-mode, knowing our external addresses has become more important.
I'm busy finishing the smart dialing effort. https://github.com/libp2p/go-libp2p/issues/2394 is the last major piece left. I will pick AutoNAT v2 implementation after next week. I'll start addressing the open issues on the specs from Monday.
So far as I understand there are two major open issues on the specs.
I'm busy finishing the smart dialing effort. libp2p/go-libp2p#2394 is the last major piece left. I will pick AutoNAT v2 implementation after next week. I'll start addressing the open issues on the specs from Monday.
Cool! I didn't mean to stress by the way, just asking! :) Looking forward to the spec discussions.
We should have a test that checks that nodes can reliably determine if they are behind a NAT. This will most likely require us to implement some kind of NAT (equivalent?), maybe using
iptables
.Main challenge: