Managing public / private IPs for peering

+1 vote
Just a question, but if I have multiple multichain nodes that all reside within a reastricted network, and then attach a peer coming in via an external IP that only has access to one designated multichain node, then as far as available peers go, my new external node will try and connect to other peers that are not reachable from the network zone it's in.

Is there a way to manage what nodes are available as peers and additionally is there a way to configure public endpoints on a peer to peer basis that could be used for peering once it's determined the private IPs are not reachable....

Hope this makes sense, but looking at a potential deployment scenario which will have a mix of nodes some being public and others private and how to manage the comms between those clusters?


asked Apr 24, 2017 by marty

1 Answer

0 votes

There are a few things that can help you with this:

  • The addnode command which can control peer-to-peer connections.
  • The addnode, bind, connect, externalip, onlynet runtime parameters inherited from Bitcoin Core. These aren't documented on the MultiChain website but you'll see them if you run multichaind with no parameters, and they're also listed here:
answered Apr 24, 2017 by MultiChain
Thanks.....I'll do some experimenting with that!