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
There are cases where e.g. exchanges want to establish outbound connections to the IF without allowing inbound connections from external nodes.
A node can be promoted to "known relation" by adding the multiaddress of the external node to the peering.json, but after adding, Hornet will continuosly try to establish a connection to the external node even if it is not wanted (or not possible because it is not reachable due to firewall restrictions).
It would be great, if outbound connections could be deactivated (e.g. by putting a ! into the DNS name of the multiaddress) - or in some other way.
The text was updated successfully, but these errors were encountered:
There are cases where e.g. exchanges want to establish outbound connections to the IF without allowing inbound connections from external nodes.
A node can be promoted to "known relation" by adding the multiaddress of the external node to the
peering.json
, but after adding, Hornet will continuosly try to establish a connection to the external node even if it is not wanted (or not possible because it is not reachable due to firewall restrictions).It would be great, if outbound connections could be deactivated (e.g. by putting a
!
into the DNS name of the multiaddress) - or in some other way.The text was updated successfully, but these errors were encountered: