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.
7563 Commits
55 Branches
107 Tags
38 MiB
Tree: afb76392e4
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'afb76392e4'
${ noResults }
lightning/connectd/connect_wire.csv

71 lines
2.7 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>
common/per_per_state: generalize lightningd/peer_comm Part 1 Encapsulating the peer state was a win for lightningd; not surprisingly, it&#39;s even more of a win for the other daemons, especially as we want to add a little gossip information. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
6 years ago
#include <common/per_peer_state.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
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgtype,connectctl_init,2000
connectd: setup chainparams We are going to signal the genesis block hash in the init message.
5 years ago
msgdata,connectctl_init,chainparams,chainparams,
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgdata,connectctl_init,id,node_id,
msgdata,connectctl_init,num_wireaddrs,u16,
msgdata,connectctl_init,wireaddrs,wireaddr_internal,num_wireaddrs
bolt-gen: use &#39;enum&#39; instead of &#39;e:&#39; prefix for enums use &#39;enum &#39; in wirespec instead of &#39;e:&#39; as an indicator that a field is an enum.
6 years ago
msgdata,connectctl_init,listen_announce,enum addr_listen_announce,num_wireaddrs
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgdata,connectctl_init,tor_proxyaddr,?wireaddr,
msgdata,connectctl_init,use_tor_proxy_always,bool,
msgdata,connectctl_init,dev_allow_localhost,bool,
msgdata,connectctl_init,use_dns,bool,
msgdata,connectctl_init,tor_password,wirestring,
Add enable-autotor-v2 config variable With enable-autotor-v2 defined in cmdline the default behavior to create v3 onions with the tor service call, is set to v2 onions. Signed-off-by: Saibato &lt;saibato.naga@pm.me&gt;
5 years ago
msgdata,connectctl_init,use_v3_autotor,bool,
connectd: Pass the init_featurebits down to connectd and use in init The `init_featurebits` are computed at startup, and then cached indefinitely. They are then used whenever a new `init` handshake is performed. We could add a new message to push updates to `connectd` whenever a plugin is added or removed, but that&#39;s up for discussion.
5 years ago
msgdata,connectctl_init,init_featurebits_len,u16,
msgdata,connectctl_init,init_featurebits,u8,init_featurebits_len
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
# Connectd->master, here are the addresses I bound, can announce.
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgtype,connectctl_init_reply,2100
msgdata,connectctl_init_reply,num_bindings,u16,
msgdata,connectctl_init_reply,bindings,wireaddr_internal,num_bindings
msgdata,connectctl_init_reply,num_announcable,u16,
msgdata,connectctl_init_reply,announcable,wireaddr,num_announcable
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
# Activate the connect daemon, so others can connect.
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgtype,connectctl_activate,2025
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
# Do we listen?
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgdata,connectctl_activate,listen,bool,
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
# Connectd->master, I am ready.
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgtype,connectctl_activate_reply,2125
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
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).
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgtype,connect_reconnected,2112
msgdata,connect_reconnected,id,node_id,
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: connect to a peer.
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgtype,connectctl_connect_to_peer,2001
msgdata,connectctl_connect_to_peer,id,node_id,
msgdata,connectctl_connect_to_peer,seconds_waited,u32,
msgdata,connectctl_connect_to_peer,addrhint,?wireaddr_internal,
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
connectd: always tell master when connection fails/succeeded. We used to separate implicit connection requests (ie. timed retries for important peers) and explicit ones, and send a WIRE_CONNECTCTL_CONNECT_TO_PEER_RESULT for the latter. In the success case, that&#39;s now redundant, since we hand the connected peer to the master using WIRE_CONNECT_PEER_CONNECTED; we just need a message for the failure case. And we might as well tell the master every failure, so we don&#39;t have to distinguish internally. This also solves a race we had before: connectd would send WIRE_CONNECTCTL_CONNECT_TO_PEER_RESULT which completes the incoming JSON connect command, then send WIRE_CONNECT_PEER_CONNECTED. So there&#39;s a window where the JSON command can return, but the peer isn&#39;t known to lightningd yet. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
6 years ago
# Connectd->master: connect failed.
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgtype,connectctl_connect_failed,2020
msgdata,connectctl_connect_failed,id,node_id,
Use dedicated type for error codes Before this patch we used `int` for error codes. The problem with `int` is that we try to pass it to/from wire and the size of `int` is not defined by the standard. So a sender with 4-byte `int` would write 4 bytes to the wire and a receiver with 2-byte `int` (for example) would read just 2 bytes from the wire. To resolve this: * Introduce an error code type with a known size: `typedef s32 errcode_t`. * Change all error code macros to constants of type `errcode_t`. Constants also play better with gdb - it would visualize the name of the constant instead of the numeric value. * Change all functions that take error codes to take the new type `errcode_t` instead of `int`. * Introduce towire / fromwire functions to send / receive the newly added type `errcode_t` and use it instead of `towire_int()`. In addition: * Remove the now unneeded `towire_int()`. * Replace a hardcoded error code `-2` with a new constant `INVOICE_EXPIRED_DURING_WAIT` (903). Changelog-Changed: The waitinvoice command would now return error code 903 to designate that the invoice expired during wait, instead of the previous -2
5 years ago
msgdata,connectctl_connect_failed,failcode,errcode_t,
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgdata,connectctl_connect_failed,failreason,wirestring,
msgdata,connectctl_connect_failed,seconds_to_delay,u32,
msgdata,connectctl_connect_failed,addrhint,?wireaddr_internal,
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
gossipd: hand a gossip_store_fd to all subdaemons. This will let them read from the gossip store directly. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
6 years ago
# Connectd -> master: we got a peer. Three fds: peer, gossip and gossip_store
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgtype,connect_peer_connected,2002
msgdata,connect_peer_connected,id,node_id,
msgdata,connect_peer_connected,addr,wireaddr_internal,
msgdata,connect_peer_connected,pps,per_peer_state,
common/features: only support a single feature bitset. This is mainly an internal-only change, especially since we don&#39;t offer any globalfeatures. However, LND (as of next release) will offer global features, and also expect option_static_remotekey to be a *global* feature. So we send our (merged) feature bitset as both global and local in init, and fold those bitsets together when we get an init msg. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
5 years ago
msgdata,connect_peer_connected,flen,u16,
msgdata,connect_peer_connected,features,u8,flen
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: peer has disconnected.
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgtype,connectctl_peer_disconnected,2015
msgdata,connectctl_peer_disconnected,id,node_id,
connectd: wire up dev_memleak. We need several notleak() annotations here: 1. The temporary structure which is handed to retry_peer_connected(). It&#39;s waiting for the master to respond to our connect_reconnected message. 2. We don&#39;t keep a pointer to the io_conn for a peer, so we need to mark those as not being a leak. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
6 years ago
# master -> connectd: do you have a memleak?
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgtype,connect_dev_memleak,2033
connectd: wire up dev_memleak. We need several notleak() annotations here: 1. The temporary structure which is handed to retry_peer_connected(). It&#39;s waiting for the master to respond to our connect_reconnected message. 2. We don&#39;t keep a pointer to the io_conn for a peer, so we need to mark those as not being a leak. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
6 years ago
wire-gen: move in-house wire delcarations to new format tidying things up!
6 years ago
msgtype,connect_dev_memleak_reply,2133
msgdata,connect_dev_memleak_reply,leak,bool,