Skip to content
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

Highlight peers in Local Area Network and in close IP space proximity #223

Closed
Kubuxu opened this issue Jan 26, 2016 · 3 comments
Closed
Labels
exp/intermediate Prior experience is likely helpful help wanted Seeking public contribution on this issue P3 Low: Not priority right now status/ready Ready to be worked

Comments

@Kubuxu
Copy link
Member

Kubuxu commented Jan 26, 2016

It would be awesome if WebUI highlighted peers that are close to you. Finding peer that is close is something that shows adaption of IPFS what is its aim.

As IP is prefix allocated (apart from cjdns) we can create following rules:

  • peerIP4 ∈ 10.0.0.0/8 - private network (RFC 1918)
  • peerIP4 ∈ 172.16.0.0/12 - private network (RFC 1918)
  • peerIP4 ∈ 192.168.0.0/16 - private network (RFC 1918)
  • peerIP4 ∈ 169.254.0.0/16 - link local (RFC 3927)
  • peerIP6 ∈ fd00::/8 - unique local address (RFC 4193)
  • peerIP6 ∈ fe80::/10 - link local (RFC 4291)
  • peerIP6 ∈ myIP6/64 - smallest end site (RFC 6177)

Also worth considering, maybe with different accent:

  • peerIP4 ∈ myIP4/24 - 255 closest users according to spatial allocation
  • peerIP6 ∈ myIP6/48 - most end sites will be allocated this prefix

where peerIP6 ∉ fc00::/8 to fix case of cjdns where IPs are not spatial allocated.

@dignifiedquire dignifiedquire added kind/discussion Topical discussion; usually not changes to codebase feature labels Jan 28, 2016
@daviddias daviddias removed the feature label Mar 17, 2018
@lidel lidel added the revamp label May 14, 2018
@olizilla olizilla added help wanted Seeking public contribution on this issue exp/intermediate Prior experience is likely helpful P3 Low: Not priority right now status/ready Ready to be worked and removed revamp kind/discussion Topical discussion; usually not changes to codebase labels Sep 27, 2018
@olizilla
Copy link
Member

This would be very cool. Related work is to add tool-tips to on hover on the peers map in #819

@ghost
Copy link

ghost commented Sep 27, 2018

  • peerIP4 ∈ myIP4/24 - 255 closest users according to spatial allocation
  • peerIP6 ∈ myIP6/48 - most end sites will be allocated this prefix

These are the smallest possible globally routable address blocks 👍 The next-bigger blocks /25 and /49 might already contain 2 completely different networks.

@hacdias
Copy link
Member

hacdias commented Feb 18, 2020

We've done it! it was released a long time ago, but here it is: #1266

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exp/intermediate Prior experience is likely helpful help wanted Seeking public contribution on this issue P3 Low: Not priority right now status/ready Ready to be worked
Projects
None yet
Development

No branches or pull requests

6 participants