Skip to content
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.

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

lightningd: don't listen at all if no port number set. #98

Merged
merged 1 commit into from
Nov 20, 2016

Conversation

rustyrussell
Copy link
Contributor

When we support the Milan protocol, we'll use a default port. But
for now, don't listen at all unless a port is specified.

Fixes: #54
Signed-off-by: Rusty Russell [email protected]

When we support the Milan protocol, we'll use a default port.  But
for now, don't listen at all unless a port is specified.

Fixes: #54
Signed-off-by: Rusty Russell <[email protected]>
@rustyrussell rustyrussell merged commit 0ba93cb into master Nov 20, 2016
@cdecker
Copy link
Member

cdecker commented Nov 21, 2016

I don't think this fully adresses #54. It avoids establishing a channel to a random port, but we may still switch the port due to manual configuration (e.g., I forgot what it was last time, let's try this one). I think we should integrate it with the node announcements instead, changing the port if we learn a new one for the node ID we are looking for.

@rustyrussell rustyrussell deleted the fix-54-dont-listen-random-port branch July 5, 2017 06:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants