lukechilds
/
lightning
mirror of https://github.com/lukechilds/lightning.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
4214 Commits
55 Branches
107 Tags
38 MiB
Tree: 337075dc8c
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '337075dc8c'
${ noResults }
lightning/connectd/connect_wire.csv

132 lines
4.8 KiB
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>
7 years ago
#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&#39;s activated. This means it doesn&#39;t know the addresses to announce until this point. Now connectd is doing this, this would mean we&#39;d have to tell gossipd later (&#34;oh, BTW here are your addresses&#34;) 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 &#34;Server started&#34;. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
#include <common/wireaddr.h>
connectd: wean off gossip_wire message types, use our own. This involves much renaming of gossip -&gt; channel. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
#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&#39;s activated. This means it doesn&#39;t know the addresses to announce until this point. Now connectd is doing this, this would mean we&#39;d have to tell gossipd later (&#34;oh, BTW here are your addresses&#34;) 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 &#34;Server started&#34;. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
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 &#39;connect_reconnected&#39; 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&#39;t maintain an fd with remote peers. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
# 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 -&gt; channel. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
# 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
# Connectd -> master: peer sent non-gossip packet. Two fds: peer and gossip
connect_peer_nongossip,2003
connect_peer_nongossip,,id,struct pubkey
connect_peer_nongossip,,addr,struct wireaddr_internal
connect_peer_nongossip,,crypto_state,struct crypto_state
connect_peer_nongossip,,gflen,u16
connect_peer_nongossip,,gfeatures,gflen*u8
connect_peer_nongossip,,lflen,u16
connect_peer_nongossip,,lfeatures,lflen*u8
connect_peer_nongossip,,len,u16
connect_peer_nongossip,,msg,len*u8
# Master -> connectd: release a peer (so we can open a channel)
connectctl_release_peer,2004
connectctl_release_peer,,id,struct pubkey
# Connectd -> master: reply to connect_release_peer. Two fds: peer and gossip.
connectctl_release_peer_reply,2104
connectctl_release_peer_reply,,addr,struct wireaddr_internal
connectctl_release_peer_reply,,crypto_state,struct crypto_state
connectctl_release_peer_reply,,gflen,u16
connectctl_release_peer_reply,,gfeatures,gflen*u8
connectctl_release_peer_reply,,lflen,u16
connectctl_release_peer_reply,,lfeatures,lflen*u8
# Connectd -> master: reply to connect_release_peer if we couldn't find the peer.
connectctl_release_peer_replyfail,2204
# master -> connectd: take back peer, with optional msg. (+peer fd, +gossip fd)
connectctl_hand_back_peer,2013
connectctl_hand_back_peer,,id,struct pubkey
connectctl_hand_back_peer,,crypto_state,struct crypto_state
connectctl_hand_back_peer,,len,u16
connectctl_hand_back_peer,,msg,len*u8
# master -> connectd: peer has disconnected.
connectctl_peer_disconnected,2015
connectctl_peer_disconnected,,id,struct pubkey
# The main daemon asks for peers
connect_getpeers_request,2011
connect_getpeers_request,,id,?struct pubkey
connect_getpeers_reply,2111
connect_getpeers_reply,,num,u16
connect_getpeers_reply,,id,num*struct pubkey
connect_getpeers_reply,,addr,num*struct wireaddr_internal
connectd: don&#39;t use gossip_getnodes_entry. gossip_getnodes_entry was used by gossipd for reporting nodes, and for reporting peers. But the local_features field is only available for peers, and most other fields are only available from node_announcement. Note that the connectd change actually means we get less information about peers: gossipd used to do the node lookup for peers and include the node_announcement information if it had it. Since generate_wire.py can&#39;t create arrays-of-arrays, we add a &#39;struct peer_features&#39; to encapsulate the two feature arrays for each peer, and for convenience we add it to lightningd/gossip_msg. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
connect_getpeers_reply,,features,num*struct peer_features
connectd: wean off gossip_wire message types, use our own. This involves much renaming of gossip -&gt; channel. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
# master->connectd: Request to disconnect from a peer.
connectctl_peer_disconnect,2023
connectctl_peer_disconnect,,id,struct pubkey
# Connectd -> master: reply to connect_peer_disconnect with peer id.
connectctl_peer_disconnect_reply,2123
# Connectd -> master: reply to connect_peer_disconnect if we couldn't find the peer.
connectctl_peer_disconnect_replyfail,2223
connectctl_peer_disconnect_replyfail,,isconnected,bool