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

Possibility to explicitly set addresses announced for libp2p #1189

Open
kuhlmannmarkus opened this issue Oct 5, 2021 · 0 comments
Open

Possibility to explicitly set addresses announced for libp2p #1189

kuhlmannmarkus opened this issue Oct 5, 2021 · 0 comments
Labels
backlog feature New feature or request

Comments

@kuhlmannmarkus
Copy link

kuhlmannmarkus commented Oct 5, 2021

Is your feature request related to a problem? Please describe.
There is no way to relay the connections. Im running a Hornet instance in my private environment. This environment can not be contacted from the outside due to the absence of a public IP address. For other applications I simply relay all the traffic on a certain port from a virtual server (that has a public address) to the machine running the app via a wireguard tunnel. This might work with Hornet for static peers (I did not test that), but autopeering will not work like this, since the node announces inaccessible addresses to the p2p network.

Describe the solution you'd like
I would suggest a config option to let me configure the addresses that get announced. IPFS does this as well and that solves my issue. Compare: https://docs.ipfs.io/how-to/configure-node/#addresses-announce

Describe alternatives you've considered
I dont see any alternative for my use case.

@kuhlmannmarkus kuhlmannmarkus added the feature New feature or request label Oct 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants