--- Log opened Thu Mar 24 00:00:35 2022
01:03 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
01:04 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnp-bp
03:52 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
03:56 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnp-bp
05:13 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
05:17 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnp-bp
05:19 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Client Quit]
06:18 < lederstrumpf[m]> hey, I can't get lnp-node peers to do the connection handshake either in the 0.5 release cycle nor with 0.6.0-beta.1
06:22 < lederstrumpf[m]> workflow is `lnp-cli -c 127.0.0.1:$RPC_PEER_A listen` -> `lnp-cli -c 127.0.0.1:$RPC_PEER_B connect $PEER_ID_PEER_A@$IP_PEER_A:9735`
06:23 < lederstrumpf[m]> then the log of `PEER_A` shows... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/8086daecfd7862dbdbdb9caea26b8d1f809c0839)
06:24 < lederstrumpf[m]> `PEER_B` gets a transport timeout
06:25 < lederstrumpf[m]> and the LNP message type is always an arbitrary even number
06:27 < lederstrumpf[m]> can also file this as a github issue if preferred - just unclear for me where in the stack the issue stems from, although I suspect internet2.
06:31 -!- DeanWeen is now known as DeanGuss
06:31 -!- DeanGuss [~dean@nonplayercharacter.me] has quit [Changing host]
06:31 -!- DeanGuss [~dean@user/deanguss] has joined #lnp-bp
19:41 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnp-bp
--- Log closed Fri Mar 25 00:00:37 2022