-
Notifications
You must be signed in to change notification settings - Fork 50
Construct addresses using MultiAddr, defaulting to IPv6 #46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Thank you @DougAnderson444 🙌 I'm guessing you tested locally?
@marten-seemann would agree 😂 , he pointed out the same in the go-peer pull request. Yeah let's enable v6!
libp2p/rust-libp2p#3625 was merged into |
Yes I tested locally, works like a charm. I didn't test on EC2 of course, I'd have to leave that to you.
Sounds great! Yes I've been watching that PR as well, glad to see mergify finally did it's thing. |
Ah, I see what you mean, |
Let's hold off on merging this for bit |
@DougAnderson444 can you fix the merge conflicts? and then I'll merge |
Yes merging now. Is there any particular reason why |
I think you can remove that and multiaddr |
I have removed the dead dependencies, and removed the dep on the rust toolchain channel (no more need for nightly to use |
Thanks for this @DougAnderson444 🚀 It seems there is still a conflict in the Cargo.toml , once that's resolved we should be good to land this. |
@maschad all deconflicted over here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Rust-Peer (server) improvements
I was working in my own repo, but I figure I would start using this repo instead of building in a parallel silo. Here are some changes I would propose for this repo.
I know this Rust server is meant for the cloud, but seeing as I am a big fan of "running a peer at home" this PR started out as changing the default IP to v6 so home servers are easier to connect, and then I added a few more cleanup items along the way. EC2 should run on IPv6 addresses just fine too, even though it has a public IP.
Summary of changes
note thatuseipv6.is_global()
is only available on nightly, I hope that's not a problem? I added a toolchain config for that. If not we can code around it with logic I suppose...!ip.is_looback()
to only add external addressesaddress_webrtc
&address_quic
)swarm
MultiAddr.with(..)
main.rs
Opt
listen_address
(String) to ensure it's a valid IP address (IpAddr
)Remaining work