vincenzopalazzo
/
rgb-cln
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity
rgb-cln/connectd/connectd.h

25 lines
740 B
C
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>
2018-09-03 04:40:00 +01:00
#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>
2018-05-10 00:18:23 +01:00
#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>
2018-09-27 22:04:19 +01:00
#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 <rusty@rustcorp.com.au>
2018-05-10 00:18:23 +01:00
struct io_conn;
connectd: rename 'struct reaching' to 'struct connecting'. It reads better, and it's accurate: it only exists while we're trying to connect to a peer. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-09-27 22:06:19 +01:00
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 '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>
2018-09-27 22:04:19 +01:00
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't get much space saving in gossipd, even though we should save 24 bytes per node. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-04-08 10:58:32 +01:00
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're about to change the message we send to lightningd, so we'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 <rusty@rustcorp.com.au> 1diff --git a/connectd/connectd.c b/connectd/connectd.c index 94fe50b56..459c9ac63 100644
2019-06-03 19:14:25 +01:00
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 <rusty@rustcorp.com.au>
2018-05-10 00:18:23 +01:00
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>
2018-09-27 22:04:19 +01:00
/* Called by io_tor_connect once it has a connection out. */
connectd: rename 'struct reaching' to 'struct connecting'. It reads better, and it's accurate: it only exists while we're trying to connect to a peer. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-09-27 22:06:19 +01:00
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 <rusty@rustcorp.com.au>
2018-05-10 00:18:23 +01:00
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>
2018-09-27 22:04:19 +01:00
/* 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're about to change the message we send to lightningd, so we'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 <rusty@rustcorp.com.au> 1diff --git a/connectd/connectd.c b/connectd/connectd.c index 94fe50b56..459c9ac63 100644
2019-06-03 19:14:25 +01:00
const struct node_id *id,
const struct wireaddr_internal *addr,
const struct crypto_state *cs,
common/features: only support a single feature bitset. This is mainly an internal-only change, especially since we don'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 <rusty@rustcorp.com.au>
2019-10-11 03:52:04 +01:00
const u8 *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 '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>
2018-09-27 22:04:19 +01:00
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>
2018-09-03 04:40:00 +01:00
#endif /* LIGHTNING_CONNECTD_CONNECTD_H */