mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2024-11-19 18:11:28 +01:00
Code Issues Projects Releases Wiki Activity
57cc4e3c34
core-lightning/lightningd/connect_control.h

21 lines
701 B
C
Raw Normal View History

lightningd/connect_control: routines to control connecting (move from peer_control.c) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-20 21:59:09 +01:00
#ifndef LIGHTNING_LIGHTNINGD_CONNECT_CONTROL_H
#define LIGHTNING_LIGHTNINGD_CONNECT_CONTROL_H
#include "config.h"
struct lightningd;
struct pubkey;
connectd: remove separate address hint message. Include it as an optional field in the connect_to_peer message (it was added before we had optional fields). The only issue is that reconnects want it too, so again connectd hands it back to master in connectctl_connect_failed. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-08-09 02:25:29 +02:00
struct wireaddr_internal;
lightningd/connect_control: routines to control connecting (move from peer_control.c) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-20 21:59:09 +01:00
gossipd: take connectd fd on initialization. connectd has a dedicated fd to gossipd, so it can ask for a new gossip_fd for a peer. gossipd has a standalone routine to create a remote peer (this will eventually be the only way gossipd creates a new peer). For now lightningd creates a socketpair but doesn't run connectd, so gossipd never sees any requests on this fd. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-07-24 08:18:58 +02:00
/* Returns fd for gossipd to talk to connectd */
int connectd_init(struct lightningd *ld);
gossipd: remove connectd functionality, enable connectd. This patch guts gossipd of all peer-related functionality, and hands all the peer-related requests to channeld instead. gossipd now gets the final announcable addresses in its init msg, since it doesn't handle socket binding any more. lightningd now actually starts connectd, and activates it. The init messages for both gossipd and connectd still contain redundant fields which need cleaning up. There are shims to handle the fact that connectd's wire messages are still (mostly) gossipd messages. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-07-24 08:18:58 +02:00
void connectd_activate(struct lightningd *ld);
connectd: remove separate address hint message. Include it as an optional field in the connect_to_peer message (it was added before we had optional fields). The only issue is that reconnects want it too, so again connectd hands it back to master in connectctl_connect_failed. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-08-09 02:25:29 +02:00
void delay_then_reconnect(struct channel *channel, u32 seconds_delay,
const struct wireaddr_internal *addrhint TAKES);
connect: return address we actually connected to. Otherwise, we might find an address other than the one given and the user might think that address worked. Fixes: #4185 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: JSON-RPC: `connect` returns `address` it actually connected to
2021-03-16 04:44:36 +01:00
void connect_succeeded(struct lightningd *ld, const struct peer *peer,
lightningd: get connection direction from connectd. This matters: if we connected, the address is probably usable for future connections. But if they connected, the port is probably not (but the IP address may be). Changelog-Added: JSON-RPC: `connect` returns "direction" ("in": they iniatated, or "out": we initiated) Changelog-Added: plugins: `peer_connected` hook and `connect` notifications have "direction" field. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-03-25 04:53:31 +01:00
bool incoming,
connect: return address we actually connected to. Otherwise, we might find an address other than the one given and the user might think that address worked. Fixes: #4185 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: JSON-RPC: `connect` returns `address` it actually connected to
2021-03-16 04:44:36 +01:00
const struct wireaddr_internal *addr);
gossipd: keep reaching struct only when we're actively connecting, and don't retry 1. Lifetime of 'struct reaching' now only while we're actively doing connect. 2. Always free after a single attempt: if it's an important peer, retry on a timer. 3. Have a single response message to master, rather than relying on peer_connected on success and other msgs on failure. 4. If we are actively connecting and we get another command for the same id, just increment the counter The result is much simpler in the master daemon, and much nicer for reconnection: if they say to connect they get an immediate response, rather than waiting for 10 retries. Even if it's an important peer, it fires off another reconnect attempt, unless it's actively connecting now. This removes exponential backoff: that's restored in next patch. It also doesn't handle multiple addresses for a single peer. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-04-26 06:50:58 +02:00
void gossip_connect_result(struct lightningd *ld, const u8 *msg);
lightningd/peer_control: reorder, move more functions out. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-20 21:59:09 +01:00
lightningd/connect_control: routines to control connecting (move from peer_control.c) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-20 21:59:09 +01:00
#endif /* LIGHTNING_LIGHTNINGD_CONNECT_CONTROL_H */
Reference in New Issue Copy Permalink