You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would enable usage of libp2p on local networks without any IP address assignment by utilizing the link-local addresses of the peers. Currently, this isn't possible, because the unix socket API requires the scope_id of a socket_addr to be set to the index of the network interface which should be used to talk to link-local IP addresses, but no libp2p transport supports this.
Requirements
Each transport that connects to unix sockets using an IPv6 address that it got from a Multiaddr (this includes at least the quic, tcp, and webrtc transports), should additionally check, if this Multiaddr also defines a zone name using the ip6zone protocol, and – if it does – should use this zone name to populate the scope_id of the socket_addr before connecting.
Open questions
No response
Are you planning to do it yourself in a pull request ?
Yes
The text was updated successfully, but these errors were encountered:
Description
libp2p should support
Multiaddr
s with theip6zone
protocol. For example, aMultiaddr
like this should be supported:Motivation
This would enable usage of libp2p on local networks without any IP address assignment by utilizing the link-local addresses of the peers. Currently, this isn't possible, because the unix socket API requires the
scope_id
of asocket_addr
to be set to the index of the network interface which should be used to talk to link-local IP addresses, but no libp2p transport supports this.Requirements
Each transport that connects to unix sockets using an IPv6 address that it got from a
Multiaddr
(this includes at least thequic
,tcp
, andwebrtc
transports), should additionally check, if thisMultiaddr
also defines a zone name using theip6zone
protocol, and – if it does – should use this zone name to populate thescope_id
of thesocket_addr
before connecting.Open questions
No response
Are you planning to do it yourself in a pull request ?
Yes
The text was updated successfully, but these errors were encountered: