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

ipfs id <self> fails #1836

Closed
richardschneider opened this issue Oct 13, 2015 · 2 comments · Fixed by #1856
Closed

ipfs id <self> fails #1836

richardschneider opened this issue Oct 13, 2015 · 2 comments · Fixed by #1856
Assignees

Comments

@richardschneider
Copy link

Supplying the local peer id to ipfs id fails with Error: routing: not found.

 D:\ipfs>ipfs id
 {
    "ID": "Qmf5A6usmhEnrRWVTvLgGbVXsMXRvj8Ja9MTv6bT77oTSY",
    "PublicKey":  ...
    "Addresses": ...
    "AgentVersion": "go-ipfs/0.3.8-dev",
    "ProtocolVersion": "ipfs/0.1.0"
 }
D:\ipfs>ipfs id Qmf5A6usmhEnrRWVTvLgGbVXsMXRvj8Ja9MTv6bT77oTSY
Error: routing: not found

Note running on a windows machine

@jbenet
Copy link
Member

jbenet commented Oct 14, 2015

this is because go-ipfs currently assumes a peerid means an online query.

  • check if given peerid is own, if so, local should be fine.
  • maybe offline routing should be able to resolve local records? cc @whyrusleeping

@whyrusleeping
Copy link
Member

offline routing can resolve local records, but i think that findpeer is written in a way that it wont return information about the asker. which is kinda weird.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants