Skip to content

Integrate nat testing tool into ipfs daemon #4352

Closed

Description

@whyrusleeping

I wrote a tool to help diagnose NAT setups: https://github.com/whyrusleeping/natest

I'm thinking we should look at integrating it into the ipfs daemon. A simple way would be to make an ipfs diag nat utility that runs the diagnostic, then advises the user on potential config changes they should make.

Slightly more interesting is doing this automatically (either on init, or on daemon startup) and automatically setting certain config options (as described here).

Activity

  1. overbool commented on Sep 9, 2018

    @overbool
    Contributor

    Hey @whyrusleeping , does this work need to continue? I found the compiling error undefined: swarm.NewNetwork in https://github.com/whyrusleeping/natest/blob/master/main.go. Maybe it should use new libp2p method.

  2. Stebalien commented on Sep 12, 2018

    @Stebalien
    Member

    It should.

  3. vyzo commented on Sep 13, 2018

    @vyzo
    Contributor

    We are planning to integrate services for NAT autodetection: see #4993.

  4. vyzo commented on Sep 13, 2018

    @vyzo
    Contributor

    Implementation WIP: libp2p/go-libp2p-autonat#1

  5. overbool commented on Sep 14, 2018

    @overbool
    Contributor

    @vyzo I'm interested in it, is there anything I can do to help?

  6. Stebalien commented on May 16, 2019

    @Stebalien
    Member

    Blocked on libp2p/go-libp2p#467. At the moment, there's no good way to access the NAT client from go-ipfs.

  7. momack2 commented on Mar 5, 2020

    @momack2
    Contributor

    Checking in on this issue - is it still blocked?

  8. Stebalien commented on Mar 5, 2020

    @Stebalien
    Member

    We've worked around the issue with an event bus. We can (once we cut a libp2p release) listen for nat routability events.

    I've filed #6951 to track printing this to stdout automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions