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

28 lines
849 B
Raw Normal View History

Put the 'd' back in the daemons. @renepickhardt: why is it actually lightningd.c with a d but hsm.c without d ? And delete unused gossipd/gossip.h. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
6 years ago
#ifndef LIGHTNING_CONNECTD_CONNECTD_H
#define LIGHTNING_CONNECTD_CONNECTD_H
gossip/tor.c: new file for socks proxy code. All gossipd needs from common/tor is do_we_use_tor_addr(), so move that and the rest of the tor-specific handshake code into gossip/tor.c Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
7 years ago
#include "config.h"
connectd/peer_exchange_initmsg: handle peer comms ourselves. connectd is the only user of the cryptomsg async APIs; better to open-code it here. We need to expose a little from cryptomsg(), but we remove the 'struct peer' entirely from connectd. One trick is that we still need to defer telling lightningd when a peer reconnects (until it tells us the old one is disconnected). So now we generate the message for lightningd and send it once we're woken. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
6 years ago
#include <bitcoin/pubkey.h>
#include <common/crypto_state.h>
gossip/tor.c: new file for socks proxy code. All gossipd needs from common/tor is do_we_use_tor_addr(), so move that and the rest of the tor-specific handshake code into gossip/tor.c Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
struct io_conn;
connectd: rename &#39;struct reaching&#39; to &#39;struct connecting&#39;. It reads better, and it&#39;s accurate: it only exists while we&#39;re trying to connect to a peer. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
6 years ago
struct connecting;
connectd/peer_exchange_initmsg: handle peer comms ourselves. connectd is the only user of the cryptomsg async APIs; better to open-code it here. We need to expose a little from cryptomsg(), but we remove the &#39;struct peer&#39; entirely from connectd. One trick is that we still need to defer telling lightningd when a peer reconnects (until it tells us the old one is disconnected). So now we generate the message for lightningd and send it once we&#39;re woken. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
6 years ago
struct daemon;
Use node_id everywhere for nodes. I tried to just do gossipd, but it was uncontainable, so this ended up being a complete sweep. We didn&#39;t get much space saving in gossipd, even though we should save 24 bytes per node. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
6 years ago
struct node_id;
connectd: generate message for lightningd inside peer_connected(). We used to generate this in the caller, then save it in case we needed to retry. We&#39;re about to change the message we send to lightningd, so we&#39;ll need to regenerate it every time; just hand all the extra args into peer_connected() and we can generate the `connect_peer_connected` msg there. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt; 1diff --git a/connectd/connectd.c b/connectd/connectd.c index 94fe50b56..459c9ac63 100644
6 years ago
struct wireaddr_internal;
gossip/tor.c: new file for socks proxy code. All gossipd needs from common/tor is do_we_use_tor_addr(), so move that and the rest of the tor-specific handshake code into gossip/tor.c Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
connectd/peer_exchange_initmsg: handle peer comms ourselves. connectd is the only user of the cryptomsg async APIs; better to open-code it here. We need to expose a little from cryptomsg(), but we remove the &#39;struct peer&#39; entirely from connectd. One trick is that we still need to defer telling lightningd when a peer reconnects (until it tells us the old one is disconnected). So now we generate the message for lightningd and send it once we&#39;re woken. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
6 years ago
/* Called by io_tor_connect once it has a connection out. */
connectd: rename &#39;struct reaching&#39; to &#39;struct connecting&#39;. It reads better, and it&#39;s accurate: it only exists while we&#39;re trying to connect to a peer. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
6 years ago
struct io_plan *connection_out(struct io_conn *conn, struct connecting *connect);
gossip/tor.c: new file for socks proxy code. All gossipd needs from common/tor is do_we_use_tor_addr(), so move that and the rest of the tor-specific handshake code into gossip/tor.c Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
connectd/connectd: Display an error hint for V3 tor onions when connect fail. @thestick613 noticed that since tor version below 0.3.2.2-alpha will not support V3 ed25519 address formats, the error handling is not that helpful in the error message from cli. So now we add an hint. Changelog-None: Signed-off-by: Saibato &lt;saibato.naga@pm.me&gt; connectd/connectd.h; Add helper function to update conn error list Signed-off-by: Saibato &lt;saibato.naga@pm.me&gt;
5 years ago
/* add erros to error list */
void add_errors_to_error_list(struct connecting *connect, const char *error);
connectd/peer_exchange_initmsg: handle peer comms ourselves. connectd is the only user of the cryptomsg async APIs; better to open-code it here. We need to expose a little from cryptomsg(), but we remove the &#39;struct peer&#39; entirely from connectd. One trick is that we still need to defer telling lightningd when a peer reconnects (until it tells us the old one is disconnected). So now we generate the message for lightningd and send it once we&#39;re woken. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
6 years ago
/* Called by peer_exchange_initmsg if successful. */
struct io_plan *peer_connected(struct io_conn *conn,
struct daemon *daemon,
connectd: generate message for lightningd inside peer_connected(). We used to generate this in the caller, then save it in case we needed to retry. We&#39;re about to change the message we send to lightningd, so we&#39;ll need to regenerate it every time; just hand all the extra args into peer_connected() and we can generate the `connect_peer_connected` msg there. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt; 1diff --git a/connectd/connectd.c b/connectd/connectd.c index 94fe50b56..459c9ac63 100644
6 years ago
const struct node_id *id,
const struct wireaddr_internal *addr,
connectd: do feature bits check after init exchange. This will help with the next patch, where we wean off using a global for features: connectd.c has access to the feature bits. Since connectd might now want to send a message, it needs the crypto_state non-const, which makes this less trivial than it would otherwise be. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
5 years ago
struct crypto_state *cs,
cleanup: make &#39;u8 *features&#39; and &#39;struct feature_set *fset&#39; more explicit. It&#39;s almost always &#34;their_features&#34; and &#34;our_features&#34; respectively, so make those names clear. Suggested-by: @cdecker Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
5 years ago
const u8 *their_features TAKES);
connectd/peer_exchange_initmsg: handle peer comms ourselves. connectd is the only user of the cryptomsg async APIs; better to open-code it here. We need to expose a little from cryptomsg(), but we remove the &#39;struct peer&#39; entirely from connectd. One trick is that we still need to defer telling lightningd when a peer reconnects (until it tells us the old one is disconnected). So now we generate the message for lightningd and send it once we&#39;re woken. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
6 years ago
Put the &#39;d&#39; back in the daemons. @renepickhardt: why is it actually lightningd.c with a d but hsm.c without d ? And delete unused gossipd/gossip.h. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
6 years ago
#endif /* LIGHTNING_CONNECTD_CONNECTD_H */