-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
add tests for AutoNAT #124
Comments
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. |
What is the progress on the V2 spec and the go implementation? I am interested in having V2 asap in |
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. So far as I understand there are two major open issues on the specs.
|
Cool! I didn't mean to stress by the way, just asking! :) |
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:
The text was updated successfully, but these errors were encountered: