Specify interface to bind while running multichaind

+1 vote
I have 2 interfaces eth0 ( internet, 11.x.x.x )  and eth1 ( LAN  , while running multichaind <chainname> , I want to specify that the the daemon should bind to than 11.x.x.x

how can I configure that?

I want to run a  private chain with my test nodes being part of the LAN (network

( haven't tried though, I think bringing down eth0 while executing the daemon might work, but I dont want to bring down the interface)

any help appreciated.



update: I am able to connect to the node via eth1 ipaddress from another node in the LAN by providing the following command

$ multichaind chain1@

but i still believe the question is valid
asked Apr 12, 2016 by sanmadhavan

1 Answer

+1 vote

We haven't yet documented this option on the MultiChain site, but you can use the bind runtime parameter to control this, which MultiChain inherits from Bitcoin Core. See this page in the bitcoin wiki: https://en.bitcoin.it/wiki/Running_Bitcoin

answered Apr 12, 2016 by MultiChain
Thanks for the reply,

-bind= option worked and i could see the following from the log:

2016-04-12 12:01:16 Bound to
2016-04-12 12:01:16 AddLocal(,2)
2016-04-12 12:01:16 init message: Loading block index...

but my daemon process stdout  still showed the following:
MultiChain Core Daemon build 1.0 alpha 19 protocol 10005

New users can connect to this node using
multichaind docRepo@115.242.x.x:4249

Node started
& in the second node (LAN, which had internet access )  when i tried to connect via public ip, (multichaind chain@115.242.x.x:4249)

i received following message:
Error: Couldn't connect to the seed node on port 4249 - please check multichaind is running at that address and that your firewall settings allow incoming connections.
however the intranet ip address (original bind address) worked
multichaind docRepo@

MultiChain Core Daemon build 1.0 alpha 19 protocol 10005

Retrieving blockchain parameters from the seed node ...
New users can connect to this node using
multichaind docRepo@

Node started

may be, its only the daemon giving incorrect address  ( in stdout message)
Yes, it's just the stdout message that's wrong. We'll fix this in the next alpha.
FYI this should be fixed in alpha 20, just released.
Thanks for the update.