lightning

1619 Commits

55 Branches

107 Tags

38 MiB

Tree: 58bf67c310

Commit Graph

Author	SHA1	Message	Date
Rusty Russell	662dfef436	lightningd/gossip: Move INIT message handling to handshake daemon. We need to do this on every connection, whether reconnecting or not, so it makes sense for the handshake daemon to handle it and return the feature fields. Longer term I'm considering having the handshake daemon handle the listening and connecting, and simply hand the fds back once the peers are ready. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago
Rusty Russell	0c8b24cf97	daemon/dns: hand netaddr we connected to through to callback. That way it doesn't have to extract it from fd. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago
Rusty Russell	f6495d3310	lightningd/peer_control: don't create peer struct until we've connected. We currently create a peer struct, then complete handshake to find out who it is. This means we have a half-formed peer, and worse: if it's a reconnect we get two peers the same. Add an explicit 'struct connection' for the handshake phase, and construct a 'struct peer' once that's done. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago

Author

SHA1

Message

Date

Rusty Russell

662dfef436

lightningd/gossip: Move INIT message handling to handshake daemon.

We need to do this on every connection, whether reconnecting or not,
so it makes sense for the handshake daemon to handle it and return
the feature fields.

Longer term I'm considering having the handshake daemon handle the
listening and connecting, and simply hand the fds back once the peers
are ready.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

8 years ago

Rusty Russell

0c8b24cf97

daemon/dns: hand netaddr we connected to through to callback.

That way it doesn't have to extract it from fd.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

8 years ago

Rusty Russell

f6495d3310

lightningd/peer_control: don't create peer struct until we've connected.

We currently create a peer struct, then complete handshake to find out
who it is.  This means we have a half-formed peer, and worse: if it's
a reconnect we get two peers the same.

Add an explicit 'struct connection' for the handshake phase, and
construct a 'struct peer' once that's done.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

8 years ago

3 Commits (58bf67c3102f64eea57127c5459b1b5b77de227a)