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
{{ message }}
This repository has been archived by the owner on May 11, 2022. It is now read-only.
Now, looking at the measurements on a local node (which was behind NAT) I managed to see multiple events constantly being emitted, even after the initial status was emitted. So the node pivots between Private and Public intermittently.
Having looked at the issues in this repo (and from our experience within the team) I know that this issue is not trivial to assume, but in the meanwhile, I'd like to ask if we can rely on this data somehow, and if we could apply some sort of a heuristic on top of this, so that the measurement becomes more credible (assuming we are only dealing with public CIDRs).
Many thanks in advance!
The text was updated successfully, but these errors were encountered:
No clue whatsoever @marten-seemann. Would you have an idea on how to actually check that? would I have to check the bind addresses for libp2p then try to telnet from another host?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi all,
We have a background worker that taps onto the events from the autonat service and propagates them to the necessary components, like so:
Now, looking at the measurements on a local node (which was behind NAT) I managed to see multiple events constantly being emitted, even after the initial status was emitted. So the node pivots between
Private
andPublic
intermittently.Having looked at the issues in this repo (and from our experience within the team) I know that this issue is not trivial to assume, but in the meanwhile, I'd like to ask if we can rely on this data somehow, and if we could apply some sort of a heuristic on top of this, so that the measurement becomes more credible (assuming we are only dealing with public CIDRs).
Many thanks in advance!
The text was updated successfully, but these errors were encountered: