core-lightning/connectd/connectd_wire.csv
Michael Schmoock 38e2abf68a peer_exchange: set, read and log remote_addr
Changelog-Added: Protocol: set remote_addr on init tlvs
2022-02-22 05:45:47 +10:30

5.1 KiB

1#include <bitcoin/block.h>
2#include <common/cryptomsg.h>
3#include <common/features.h>
4#include <common/node_id.h>
5#include <common/wireaddr.h>
6#include <wire/onion_wire.h>
7msgtype,connectd_init,2000
8msgdata,connectd_init,chainparams,chainparams,
9msgdata,connectd_init,our_features,feature_set,
10msgdata,connectd_init,id,node_id,
11msgdata,connectd_init,num_wireaddrs,u16,
12msgdata,connectd_init,wireaddrs,wireaddr_internal,num_wireaddrs
13msgdata,connectd_init,listen_announce,enum addr_listen_announce,num_wireaddrs
14msgdata,connectd_init,tor_proxyaddr,?wireaddr,
15msgdata,connectd_init,use_tor_proxy_always,bool,
16msgdata,connectd_init,dev_allow_localhost,bool,
17msgdata,connectd_init,use_dns,bool,
18msgdata,connectd_init,tor_password,wirestring,
19msgdata,connectd_init,use_v3_autotor,bool,
20msgdata,connectd_init,timeout_secs,u32,
21msgdata,connectd_init,websocket_helper,wirestring,
22msgdata,connectd_init,websocket_port,u16,
23msgdata,connectd_init,dev_fast_gossip,bool,
24# If this is set, then fd 5 is dev_disconnect_fd.
25msgdata,connectd_init,dev_disconnect,bool,
26# Connectd->master, here are the addresses I bound, can announce.
27msgtype,connectd_init_reply,2100
28msgdata,connectd_init_reply,num_bindings,u16,
29msgdata,connectd_init_reply,bindings,wireaddr_internal,num_bindings
30msgdata,connectd_init_reply,num_announcable,u16,
31msgdata,connectd_init_reply,announcable,wireaddr,num_announcable
32# Activate the connect daemon, so others can connect.
33msgtype,connectd_activate,2025
34# Do we listen?
35msgdata,connectd_activate,listen,bool,
36# Connectd->master, I am ready.
37msgtype,connectd_activate_reply,2125
38# connectd->master: disconnect this peer please (due to reconnect).
39msgtype,connectd_reconnected,2112
40msgdata,connectd_reconnected,id,node_id,
41# Master -> connectd: connect to a peer.
42msgtype,connectd_connect_to_peer,2001
43msgdata,connectd_connect_to_peer,id,node_id,
44msgdata,connectd_connect_to_peer,seconds_waited,u32,
45msgdata,connectd_connect_to_peer,len,u32,
46msgdata,connectd_connect_to_peer,addrs,wireaddr,len
47msgdata,connectd_connect_to_peer,addrhint,?wireaddr_internal,
48# Connectd->master: connect failed.
49msgtype,connectd_connect_failed,2020
50msgdata,connectd_connect_failed,id,node_id,
51msgdata,connectd_connect_failed,failcode,errcode_t,
52msgdata,connectd_connect_failed,failreason,wirestring,
53msgdata,connectd_connect_failed,seconds_to_delay,u32,
54msgdata,connectd_connect_failed,addrhint,?wireaddr_internal,
55# Connectd -> master: we got a peer. Plus fd for peer daemon
56msgtype,connectd_peer_connected,2002
57msgdata,connectd_peer_connected,id,node_id,
58msgdata,connectd_peer_connected,addr,wireaddr_internal,
59msgdata,connectd_peer_connected,remote_addr,?wireaddr,
60msgdata,connectd_peer_connected,incoming,bool,
61msgdata,connectd_peer_connected,flen,u16,
62msgdata,connectd_peer_connected,features,u8,flen
63# master -> connectd: peer has disconnected.
64msgtype,connectd_peer_disconnected,2015
65msgdata,connectd_peer_disconnected,id,node_id,
66# master -> connectd: give message to peer and disconnect.
67msgtype,connectd_peer_final_msg,2003
68msgdata,connectd_peer_final_msg,id,node_id,
69msgdata,connectd_peer_final_msg,len,u16,
70msgdata,connectd_peer_final_msg,msg,u8,len
71# master -> connectd: do you have a memleak?
72msgtype,connectd_dev_memleak,2033
73msgtype,connectd_dev_memleak_reply,2133
74msgdata,connectd_dev_memleak_reply,leak,bool,
75# Ping/pong test. Waits for a reply if it expects one.
76msgtype,connectd_ping,2030
77msgdata,connectd_ping,id,node_id,
78msgdata,connectd_ping,num_pong_bytes,u16,
79msgdata,connectd_ping,len,u16,
80msgtype,connectd_ping_reply,2130
81# False if we there was already a ping in progress.
82msgdata,connectd_ping_reply,sent,bool,
83# 0 == no pong expected, otherwise length of pong.
84msgdata,connectd_ping_reply,totlen,u16,
85# We tell lightningd we got an onionmsg
86msgtype,connectd_got_onionmsg_to_us,2145
87msgdata,connectd_got_onionmsg_to_us,obs2,bool,
88msgdata,connectd_got_onionmsg_to_us,node_alias,pubkey,
89msgdata,connectd_got_onionmsg_to_us,self_id,?secret,
90msgdata,connectd_got_onionmsg_to_us,reply_blinding,?pubkey,
91msgdata,connectd_got_onionmsg_to_us,reply_first_node,?pubkey,
92msgdata,connectd_got_onionmsg_to_us,reply_path_len,u16,
93msgdata,connectd_got_onionmsg_to_us,reply_path,onionmsg_path,reply_path_len
94msgdata,connectd_got_onionmsg_to_us,rawmsg_len,u16,
95msgdata,connectd_got_onionmsg_to_us,rawmsg,u8,rawmsg_len
96# Lightningd tells us to send an onion message.
97msgtype,connectd_send_onionmsg,2041
98msgdata,connectd_send_onionmsg,obs2,bool,
99msgdata,connectd_send_onionmsg,id,node_id,
100msgdata,connectd_send_onionmsg,onion_len,u16,
101msgdata,connectd_send_onionmsg,onion,u8,onion_len
102msgdata,connectd_send_onionmsg,blinding,pubkey,
103# A custom message that we got from a peer and don't know how to handle, so we
104# forward it to the master for further handling.
105msgtype,connectd_custommsg_in,2110
106msgdata,connectd_custommsg_in,id,node_id,
107msgdata,connectd_custommsg_in,msg_len,u16,
108msgdata,connectd_custommsg_in,msg,u8,msg_len
109# A custom message that the lightningd tells us to send to the peer.
110msgtype,connectd_custommsg_out,2011
111msgdata,connectd_custommsg_out,id,node_id,
112msgdata,connectd_custommsg_out,msg_len,u16,
113msgdata,connectd_custommsg_out,msg,u8,msg_len