Skip to content

Opening a second channel from eclair to c-lightning causes that and previously existing channel to be closed. #494

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.

Sign up for GitHub

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

Jump to bottom
Closed
ephraim71 opened this issue Jan 1, 2018 · 1 comment
Closed

Opening a second channel from eclair to c-lightning causes that and previously existing channel to be closed. #494

ephraim71 opened this issue Jan 1, 2018 · 1 comment
Assignees
@rustyrussell

Comments

@ephraim71
Copy link
Contributor

So c-lightning supports one channel/peer.
When eclair tries to open a second channel, the first channel also closes.
same as ACINQ/eclair#351
lightningd log - lightningc.txt
@ZmnSCPxj
Copy link
Contributor

ZmnSCPxj commented Jan 4, 2018

Can this be merged with #287? To my mind, to "fail gracefully" on the second channel open, should fail only the second channel open while keep existing channel.

@rustyrussell rustyrussell self-assigned this Jan 10, 2018
rustyrussell added a commit to rustyrussell/lightning that referenced this issue Jan 10, 2018
@rustyrussell
channeld: ignore spurious open_channel packets.
67dcf9d 
Currently we peer_failed() which fails the existing channel too!

Fixes: ElementsProject#494
Signed-off-by: Rusty Russell <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rustyrussell rustyrussell

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rustyrussell @ephraim71 @ZmnSCPxj