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
Currently, if we receive an incoming connection, then the port we store in the database for the IP address that made that incoming connection is the port the TCP connection was assigned to after the initial handshake completed. Upon boot (if we later establish a channel with that node), the daemon will then tell the connmgr to establish a persistent connection to that peer, however the connection will fail indefinitely as it's attempting to use the non-default TCP port.
The logic around establishing persistent connections should be modified to instead store the advertise IP+port information within the peer's NodeAnnouncement rather than the information we obtain upon connection.
The text was updated successfully, but these errors were encountered:
Currently, if we receive an incoming connection, then the port we store in the database for the IP address that made that incoming connection is the port the TCP connection was assigned to after the initial handshake completed. Upon boot (if we later establish a channel with that node), the daemon will then tell the
connmgr
to establish a persistent connection to that peer, however the connection will fail indefinitely as it's attempting to use the non-default TCP port.The logic around establishing persistent connections should be modified to instead store the advertise IP+port information within the peer's
NodeAnnouncement
rather than the information we obtain upon connection.The text was updated successfully, but these errors were encountered: