Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Peers are unable to reconnect and stuck in a deadlock after IP address change

See original GitHub issue

Issue Description

As described by @t-bast in https://gitter.im/ACINQ/eclair LND and eclair (possibly c-lightning) peers are unable to reconnect after a IP address change due to not trusting node_announcement:

if you change your IP address, your peers won’t reconnect to you. They’ll wait for you to connect to them and then will store your new IP address for future reconnections (ie they don’t trust the new IP address from node_announcement alone)

This leads to a situation where even some clearnet peers have to be manually reconnected which can be quite time consuming and TOR peers are stuck in a deadlock that can only manually be resolved by the node operator of each and every TOR peer. They would have to look up the new IP address of their offline peer on one of the lightning explorer websites and manually feed it to their node. This is unlikely to happen quickly, if at all.

I changed the IP of my node more than 2 days ago and still have 65 disconnected TOR peers. Most, if not all of them seem to be running LND.

I’d suggest to use the IP from node_announcement if a connection to the last known IP fails. Can still be alternated with last known IP until success.

Also reported to LND: https://github.com/lightningnetwork/lnd/issues/5377

Issue Analytics

State:
Created 2 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

t-bastcommented, Sep 27, 2021

@pm47 I’d be curious to have your input on this as it impacts the (re)connection logic. It feels like we could be smarter when reconnecting, and try the address from the latest node_announcement if the last address we know doesn’t work.

0reactions

t-bastcommented, Feb 1, 2022

This should be fixed by #2123, feel free to reopen if it isn’t.

Top Results From Across the Web

Peers are still unable to reconnect and stuck in a deadlock ...

I had another IP address change on my node and around 25 of my tor peers are still disconnected after 40 hours. The...

How to fix the “Failed to obtain IP address” error on Android

Reconnect to a network · Assign a static IP to your device · Restart your router or a mobile device · Change the...

Critical Issues Addressed in PAN-OS Releases

Bugs Affected Platform(if any). /Affected Version Description (release note) PAN‑92564 8.0.0‑8.0‑8, 8.1.0 PAN‑86882 8.0.0‑8.0.7. and all older Mainlines PAN‑81990 PA‑5220,PA‑5250. /. 8.0.4 Multiple DP restarts by...

How to solve dist.init_process_group from hanging (or ...

We have been using the environment variable initialization method throughout this tutorial. By setting the following four environment variables ...

Supplemental Document: BIG-IP 16.1.2 Fixes and Known Issues

When a BIG-IP system is configured to work with BIG-IQ but cannot connect due ... After changing management IP addresses, devices can be...