Michael Eckhoff (K5MRE)
I'm attempting to add a second IPSC peer to an existing peer group and finding that when the two peers attempt to register with each other, it's not working. In addition, after a while, they drop their connection to the master as well.
On one peer, I get the following in the logs:
INFO 2018-10-15 22:25:17,060 (MASTER) Registering with the Master: x.x.x.x:64835
WARNING 2018-10-15 22:25:17,702 (MASTER) Registration response (we requested reg) from the Master: 1315835, x.x.x.x:64835 (1 peers)
INFO 2018-10-15 22:25:22,064 (MASTER), No Peer List - Requesting One From the Master
INFO 2018-10-15 22:25:24,171 (MASTER) Peer List Received from Master: 2 peers in this IPSC
INFO 2018-10-15 22:25:27,063 (MASTER) Registering with Peer 315835, 220.127.116.11:50000
INFO 2018-10-15 22:25:32,065 (MASTER) Registering with Peer 315835, 18.104.22.168:50000
INFO 2018-10-15 22:25:37,065 (MASTER) Registering with Peer 315835, 22.214.171.124:50000
INFO 2018-10-15 22:25:42,065 (MASTER) Registering with Peer 315835, 126.96.36.199:50000
INFO 2018-10-15 22:25:47,065 (MASTER) Registering with Peer 315835, 188.8.131.52:50000
And on the other peer, there's no registration attempt after it gets the alert that there's an additional peer from the master.
I can see in the debug logs that both peers are getting a new peer list and that each of the peers is on it. It's just that the one peer never tries to do the registration with the other, but the second peer does.
From the DO_NOT_README file, it makes it clear that all peers try to register with each other, and that process is part of the reason as to how the pinholes get setup in the NATs/FWs. But if one of the peers doesn't try, then the pinholes never get setup, which is I assume why the peer that is trying to register isn't actually able to do it.
1. Why wouldn't one of the two peers be attempting to reach out to the other, but one does? Is there some kind of election by highest/lowest ID or something that dictates who goes first or should they both always blinding just reach out to each other?
2. Why does the master drop the connection to both peers because the two peers can't talk to each other? I would expect the master to stay connected and the peers just end up being islands. Note: I don't see anything in the logs when the master does this, however, I can see on the C-Bridge that they've been disconnected.
3. I only have a configuration for the MASTER. I have no configuration setup for PEERS, as it appears to be getting that info from the master. Do I need a peer configuration?
I've tried this with both the branches and get the same result - and it's always the same peer that tries to reach out to the other.