Skip to content

fix: re-expose AutoNAT service on BasicHost#1088

Merged
Stebalien merged 1 commit into
masterfrom
feat/expose-autonat
May 5, 2021
Merged

fix: re-expose AutoNAT service on BasicHost#1088
Stebalien merged 1 commit into
masterfrom
feat/expose-autonat

Conversation

@Stebalien

Copy link
Copy Markdown
Member

Unfortunately, lotus relies on this and we don't have a good alternative at the moment.

  1. The "correct" way to get the status is to subscribe to the "discoverability" events and read the first event (you're guaranteed to see a "current status" event). However, this is a bit annoying.
  2. Ideally, you'd call host.Addrs() to get the list of "good" addresses. Unfortunately, we don't feed enough information back into the Host from AutoNAT for this to be truly useful (yet).

Unfortunately, lotus relies on this and we don't have a good alternative
at the moment.

1. The "correct" way to get the status is to subscribe to the
"discoverability" events and read the first event (you're guaranteed to
see a "current status" event). However, this is a bit annoying.
2. Ideally, you'd call host.Addrs() to get the list of "good" addresses.
Unfortunately, we don't feed enough information back into the Host from
AutoNAT for this to be truly useful (yet).
@Stebalien Stebalien merged commit 3e5c305 into master May 5, 2021
@Stebalien Stebalien deleted the feat/expose-autonat branch May 5, 2021 03:39
@Stebalien Stebalien mentioned this pull request May 11, 2021
27 tasks
@aschmahmann aschmahmann mentioned this pull request May 14, 2021
71 tasks
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 this pull request may close these issues.

2 participants