mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2025-01-07 14:29:33 +01:00
Code Issues Projects Releases Wiki Activity
684d60dbda
core-lightning/connectd/connect_wire.csv

76 lines
2.7 KiB
Plaintext
Raw Normal View History

connectd: wean off gossip_wire message types, use our own. This involves much renaming of gossip -> channel. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-07-24 08:18:58 +02:00
#include <common/cryptomsg.h>
connectd: do socket binding during initial setup. gossipd does a two-step initialization: it only tries to create the listening sockets when it's activated. This means it doesn't know the addresses to announce until this point. Now connectd is doing this, this would mean we'd have to tell gossipd later ("oh, BTW here are your addresses") since we need to start gossipd before connectd activation. So make connectd do all the setup, but only actually listen on the fds once we activate it. We clone the gossip_init message into connect_wire.csv. The master daemon still waits for a reply from connectd for the activate message, since it wants to be listening before it prints "Server started". Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-07-24 08:18:58 +02:00
#include <common/wireaddr.h>
connectd: wean off gossip_wire message types, use our own. This involves much renaming of gossip -> channel. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-07-24 08:18:58 +02:00
#include <lightningd/gossip_msg.h>
connectd: do socket binding during initial setup. gossipd does a two-step initialization: it only tries to create the listening sockets when it's activated. This means it doesn't know the addresses to announce until this point. Now connectd is doing this, this would mean we'd have to tell gossipd later ("oh, BTW here are your addresses") since we need to start gossipd before connectd activation. So make connectd do all the setup, but only actually listen on the fds once we activate it. We clone the gossip_init message into connect_wire.csv. The master daemon still waits for a reply from connectd for the activate message, since it wants to be listening before it prints "Server started". Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-07-24 08:18:58 +02:00
connectctl_init,2000
connectctl_init,,id,struct pubkey
connectctl_init,,gflen,u16
connectctl_init,,gfeatures,gflen*u8
connectctl_init,,lflen,u16
connectctl_init,,lfeatures,lflen*u8
connectctl_init,,num_wireaddrs,u16
connectctl_init,,wireaddrs,num_wireaddrs*struct wireaddr_internal
connectctl_init,,listen_announce,num_wireaddrs*enum addr_listen_announce
connectctl_init,,reconnect,bool
connectctl_init,,tor_proxyaddr,?struct wireaddr
connectctl_init,,use_tor_proxy_always,bool
connectctl_init,,dev_allow_localhost,bool
connectctl_init,,use_dns,bool
connectctl_init,,tor_password,wirestring
# Connectd->master, here are the addresses I bound, can announce.
connectctl_init_reply,2100
connectctl_init_reply,,num_bindings,u16
connectctl_init_reply,,bindings,num_bindings*struct wireaddr_internal
connectctl_init_reply,,num_announcable,u16
connectctl_init_reply,,announcable,num_announcable*struct wireaddr
# Activate the connect daemon, so others can connect.
connectctl_activate,2025
# Do we listen?
connectctl_activate,,listen,bool
# Connectd->master, I am ready.
connectctl_activate_reply,2125
connectd: new daemon to handle connections. This is just copying most of gossipd/gossip.c into connectd/connect.c. It shares the same wire format as gossipd during transition, and changes are deliberately minimal. It also has an additional message 'connect_reconnected' which it sends to the master daemon to tell it to kill a peer; gossipd relied on closing the gossipfd to do this, but connectd doesn't maintain an fd with remote peers. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-07-24 08:18:58 +02:00
# connectd->master: disconnect this peer please (due to reconnect).
connect_reconnected,2112
connect_reconnected,,id,struct pubkey
connectd: wean off gossip_wire message types, use our own. This involves much renaming of gossip -> channel. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-07-24 08:18:58 +02:00
# Master -> connectd: Optional hint for where to find peer.
connectctl_peer_addrhint,2014
connectctl_peer_addrhint,,id,struct pubkey
connectctl_peer_addrhint,,addr,struct wireaddr_internal
# Master -> connectd: connect to a peer.
connectctl_connect_to_peer,2001
connectctl_connect_to_peer,,id,struct pubkey
# Connectd->master: result (not a reply since it can be out-of-order, but
# you will get one reply for every request).
connectctl_connect_to_peer_result,2020
connectctl_connect_to_peer_result,,id,struct pubkey
# True it connected.
connectctl_connect_to_peer_result,,connected,bool
# Otherwise, why we can't reach them.
connectctl_connect_to_peer_result,,failreason,wirestring
# Master -> connectd: try to always maintain connection to this peer (or not)
connectctl_peer_important,2010
connectctl_peer_important,,id,struct pubkey
connectctl_peer_important,,important,bool
# Connectd -> master: we got a peer. Two fds: peer and gossip
connect_peer_connected,2002
connect_peer_connected,,id,struct pubkey
connect_peer_connected,,addr,struct wireaddr_internal
connect_peer_connected,,crypto_state,struct crypto_state
connect_peer_connected,,gflen,u16
connect_peer_connected,,gfeatures,gflen*u8
connect_peer_connected,,lflen,u16
connect_peer_connected,,lfeatures,lflen*u8
# master -> connectd: peer has disconnected.
connectctl_peer_disconnected,2015
connectctl_peer_disconnected,,id,struct pubkey
Reference in New Issue Copy Permalink