run seed in a vm with public internet ip address.
# go run seed.go
2020/12/01 16:25:11 [119 42 39 175 216 103 81 128 232 108 136 240 198 14 94 8 233 51 80 60 186 249 108 87 28 181 134 16 75 78 216 212]
2020/12/01 16:25:11 nnet: {tcp [tcp kcp] SOME_REMOTE_ADDR 23333 32 8 smux 8 32 23333 23333 1 [BROADCAST_PUSH] 5m0s 10s 2333 2333 [BROADCAST_PUSH] 5m0s 10s 20971520 5s 1s 5s 20s 5s 23333 8 3 2 2s}
run peer in my laptop.
# go run peer.go
2020/12/02 08:17:16 id: [163 45 97 232 127 118 238 34 253 54 242 96 120 114 175 75 26 233 40 149 79 93 50 161 202 2 78 235 63 210 218 117]
2020/12/02 08:17:16 nnet: {tcp [tcp kcp] SOME_REMOTE_ADDR 23333 32 8 smux 8 32 23333 23333 1 [BROADCAST_PUSH] 5m0s 10s 2333 2333 [BROADCAST_PUSH] 5m0s 10s 20971520 5s 1s 5s 20s 5s 23333 8 3 2 2s}
2020/12/02 08:17:16 Remote node connect from 127.0.0.1:53637 to local address 127.0.0.1:23333
2020/12/02 08:17:16 Join
2020/12/02 08:17:16 Remote node <127.0.0.1:53637> stops because of error: Chord node is not ready yet
2020/12/02 08:17:16 Remote node <127.0.0.1:23333> stops because of error: Node addr tcp://:23333 is different from expected value tcp://SOME_REMOTE_ADDR:23333
2020/12/02 08:17:16 Handle remote message error: Node addr tcp://:23333 is different from expected value tcp://SOME_REMOTE_ADDR:23333
2020/12/02 08:17:16 Received stop message from remote node <127.0.0.1:23333>
2020/12/02 08:17:16 Received stop message from remote node <127.0.0.1:53637>