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
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.
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.
The text was updated successfully, but these errors were encountered: