Running multiple Bitcoin nodes on same network

I want to run a bitcoin node two separate devices (computer + dedicated hardware device) on the same network (and would like them to be externally accessible).

I've read it is critical that you forward port 8333 on your router to the IP address of the computer that is running your node, so I'm not sure what to do on the dedicated hardware device then.

I've seen you can add port and rpcport arguments to the bitcoin.conf file, but I'm can't figure out exactly how this setup will work on the same network with two different bitcoin nodes.

Any help by someone more expert (most people likely ha) than me would be appreciated, thanks!

Bitcoin.conf file

daemon=1

server=1

prune=750

zmqpubrawblock=tcp://127.0.0.1:28332

zmqpubrawtx=tcp://127.0.0.1:28333

rpcuser=xxx

rpcpassword=xxx

edited Nov 29 '18 at 22:17

asked Nov 28 '18 at 22:18

SRMR

83331942

If you can post your configuration file, that will be great.

– tim
Nov 28 '18 at 22:27

@tim sure! Updated my question with the conf file info. Today I tried adding rpcport=8332 to it, but realized I didn't really know what I was doing there to have clarity, so I decided to ask a question.

– SRMR
Nov 28 '18 at 22:37

This doesn't appear to be about programming. You may be able to get help on our sister site Bitcoin.

– Michael Hampton
Nov 30 '18 at 2:36

@MichaelHampton hey my bad! thanks for the heads up, I will post over there instead. thanks!

– SRMR
Nov 30 '18 at 2:42

add a comment |

I want to run a bitcoin node two separate devices (computer + dedicated hardware device) on the same network (and would like them to be externally accessible).

I've read it is critical that you forward port 8333 on your router to the IP address of the computer that is running your node, so I'm not sure what to do on the dedicated hardware device then.

I've seen you can add port and rpcport arguments to the bitcoin.conf file, but I'm can't figure out exactly how this setup will work on the same network with two different bitcoin nodes.

Any help by someone more expert (most people likely ha) than me would be appreciated, thanks!

Bitcoin.conf file

daemon=1

server=1

prune=750

zmqpubrawblock=tcp://127.0.0.1:28332

zmqpubrawtx=tcp://127.0.0.1:28333

rpcuser=xxx

rpcpassword=xxx

edited Nov 29 '18 at 22:17

asked Nov 28 '18 at 22:18

SRMR

83331942

If you can post your configuration file, that will be great.

– tim
Nov 28 '18 at 22:27

@tim sure! Updated my question with the conf file info. Today I tried adding rpcport=8332 to it, but realized I didn't really know what I was doing there to have clarity, so I decided to ask a question.

– SRMR
Nov 28 '18 at 22:37

This doesn't appear to be about programming. You may be able to get help on our sister site Bitcoin.

– Michael Hampton
Nov 30 '18 at 2:36

@MichaelHampton hey my bad! thanks for the heads up, I will post over there instead. thanks!

– SRMR
Nov 30 '18 at 2:42

add a comment |

I want to run a bitcoin node two separate devices (computer + dedicated hardware device) on the same network (and would like them to be externally accessible).

I've read it is critical that you forward port 8333 on your router to the IP address of the computer that is running your node, so I'm not sure what to do on the dedicated hardware device then.

I've seen you can add port and rpcport arguments to the bitcoin.conf file, but I'm can't figure out exactly how this setup will work on the same network with two different bitcoin nodes.

Any help by someone more expert (most people likely ha) than me would be appreciated, thanks!

Bitcoin.conf file

daemon=1

server=1

prune=750

zmqpubrawblock=tcp://127.0.0.1:28332

zmqpubrawtx=tcp://127.0.0.1:28333

rpcuser=xxx

rpcpassword=xxx

edited Nov 29 '18 at 22:17

asked Nov 28 '18 at 22:18

SRMR

83331942

I want to run a bitcoin node two separate devices (computer + dedicated hardware device) on the same network (and would like them to be externally accessible).

I've read it is critical that you forward port 8333 on your router to the IP address of the computer that is running your node, so I'm not sure what to do on the dedicated hardware device then.

I've seen you can add port and rpcport arguments to the bitcoin.conf file, but I'm can't figure out exactly how this setup will work on the same network with two different bitcoin nodes.

Any help by someone more expert (most people likely ha) than me would be appreciated, thanks!

Bitcoin.conf file

daemon=1

server=1

prune=750

zmqpubrawblock=tcp://127.0.0.1:28332

zmqpubrawtx=tcp://127.0.0.1:28333

rpcuser=xxx

rpcpassword=xxx

bitcoin bitcoind

edited Nov 29 '18 at 22:17

asked Nov 28 '18 at 22:18

SRMR

83331942

edited Nov 29 '18 at 22:17

asked Nov 28 '18 at 22:18

SRMR

83331942

edited Nov 29 '18 at 22:17

asked Nov 28 '18 at 22:18

SRMR

83331942

asked Nov 28 '18 at 22:18

SRMR

83331942

asked Nov 28 '18 at 22:18

SRMR

83331942

If you can post your configuration file, that will be great.

– tim
Nov 28 '18 at 22:27

@tim sure! Updated my question with the conf file info. Today I tried adding rpcport=8332 to it, but realized I didn't really know what I was doing there to have clarity, so I decided to ask a question.

– SRMR
Nov 28 '18 at 22:37

This doesn't appear to be about programming. You may be able to get help on our sister site Bitcoin.

– Michael Hampton
Nov 30 '18 at 2:36

@MichaelHampton hey my bad! thanks for the heads up, I will post over there instead. thanks!

– SRMR
Nov 30 '18 at 2:42

add a comment |

If you can post your configuration file, that will be great.

– tim
Nov 28 '18 at 22:27

@tim sure! Updated my question with the conf file info. Today I tried adding rpcport=8332 to it, but realized I didn't really know what I was doing there to have clarity, so I decided to ask a question.

– SRMR
Nov 28 '18 at 22:37

This doesn't appear to be about programming. You may be able to get help on our sister site Bitcoin.

– Michael Hampton
Nov 30 '18 at 2:36

@MichaelHampton hey my bad! thanks for the heads up, I will post over there instead. thanks!

– SRMR
Nov 30 '18 at 2:42

If you can post your configuration file, that will be great.

– tim
Nov 28 '18 at 22:27

@tim sure! Updated my question with the conf file info. Today I tried adding rpcport=8332 to it, but realized I didn't really know what I was doing there to have clarity, so I decided to ask a question.

– SRMR
Nov 28 '18 at 22:37

This doesn't appear to be about programming. You may be able to get help on our sister site Bitcoin.

– Michael Hampton
Nov 30 '18 at 2:36

@MichaelHampton hey my bad! thanks for the heads up, I will post over there instead. thanks!

– SRMR
Nov 30 '18 at 2:42

add a comment |

1 Answer
1

active

oldest

votes

It is not true that you have to forward port 8333. Bitcoin works just as fine without your node being externally accessible. If you want a connection between both of your local two nodes, just use the "addnode" flag with their LAN address.

answered Nov 29 '18 at 22:03

Skriptkiddie

3157

Thanks for the response. I would like the nodes to be externally accessible (be able to take inbound is what I'm talking about), in which case does that change anything about your answer? And I don't want a connection between both of my two local nodes, sorry if that part wasn't clear.

– SRMR
Nov 29 '18 at 22:16

You will have to run one of the nodes on a different p2p port than 8333. This is perfectly fine, since getaddr will advertise your ip address anlong with the port. One thing you should to is either use UPNP or specify the external address using the "bind" option and take care of the NAT tables in your router yourself. Otherwise the node will only know its local LAN address, flag it as "not accessible" and not broadcast your address at all; that would mean that even if your node is externally accessible, nobody would access it!

– Skriptkiddie
Nov 29 '18 at 22:35

Cool, thanks for the explanation! I will give it a try!

– SRMR
Nov 30 '18 at 2:43

add a comment |

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53528960%2frunning-multiple-bitcoin-nodes-on-same-network%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

answered Nov 29 '18 at 22:03

Skriptkiddie

3157

Thanks for the response. I would like the nodes to be externally accessible (be able to take inbound is what I'm talking about), in which case does that change anything about your answer? And I don't want a connection between both of my two local nodes, sorry if that part wasn't clear.

– SRMR
Nov 29 '18 at 22:16

You will have to run one of the nodes on a different p2p port than 8333. This is perfectly fine, since getaddr will advertise your ip address anlong with the port. One thing you should to is either use UPNP or specify the external address using the "bind" option and take care of the NAT tables in your router yourself. Otherwise the node will only know its local LAN address, flag it as "not accessible" and not broadcast your address at all; that would mean that even if your node is externally accessible, nobody would access it!

– Skriptkiddie
Nov 29 '18 at 22:35

Cool, thanks for the explanation! I will give it a try!

– SRMR
Nov 30 '18 at 2:43

add a comment |

answered Nov 29 '18 at 22:03

Skriptkiddie

3157

Thanks for the response. I would like the nodes to be externally accessible (be able to take inbound is what I'm talking about), in which case does that change anything about your answer? And I don't want a connection between both of my two local nodes, sorry if that part wasn't clear.

– SRMR
Nov 29 '18 at 22:16

You will have to run one of the nodes on a different p2p port than 8333. This is perfectly fine, since getaddr will advertise your ip address anlong with the port. One thing you should to is either use UPNP or specify the external address using the "bind" option and take care of the NAT tables in your router yourself. Otherwise the node will only know its local LAN address, flag it as "not accessible" and not broadcast your address at all; that would mean that even if your node is externally accessible, nobody would access it!

– Skriptkiddie
Nov 29 '18 at 22:35

Cool, thanks for the explanation! I will give it a try!

– SRMR
Nov 30 '18 at 2:43

add a comment |

answered Nov 29 '18 at 22:03

Skriptkiddie

3157

answered Nov 29 '18 at 22:03

Skriptkiddie

3157

answered Nov 29 '18 at 22:03

Skriptkiddie

3157

answered Nov 29 '18 at 22:03

Skriptkiddie

3157

answered Nov 29 '18 at 22:03

Skriptkiddie

3157

Thanks for the response. I would like the nodes to be externally accessible (be able to take inbound is what I'm talking about), in which case does that change anything about your answer? And I don't want a connection between both of my two local nodes, sorry if that part wasn't clear.

– SRMR
Nov 29 '18 at 22:16

You will have to run one of the nodes on a different p2p port than 8333. This is perfectly fine, since getaddr will advertise your ip address anlong with the port. One thing you should to is either use UPNP or specify the external address using the "bind" option and take care of the NAT tables in your router yourself. Otherwise the node will only know its local LAN address, flag it as "not accessible" and not broadcast your address at all; that would mean that even if your node is externally accessible, nobody would access it!

– Skriptkiddie
Nov 29 '18 at 22:35

Cool, thanks for the explanation! I will give it a try!

– SRMR
Nov 30 '18 at 2:43

add a comment |

Thanks for the response. I would like the nodes to be externally accessible (be able to take inbound is what I'm talking about), in which case does that change anything about your answer? And I don't want a connection between both of my two local nodes, sorry if that part wasn't clear.

– SRMR
Nov 29 '18 at 22:16

You will have to run one of the nodes on a different p2p port than 8333. This is perfectly fine, since getaddr will advertise your ip address anlong with the port. One thing you should to is either use UPNP or specify the external address using the "bind" option and take care of the NAT tables in your router yourself. Otherwise the node will only know its local LAN address, flag it as "not accessible" and not broadcast your address at all; that would mean that even if your node is externally accessible, nobody would access it!

– Skriptkiddie
Nov 29 '18 at 22:35

Cool, thanks for the explanation! I will give it a try!

– SRMR
Nov 30 '18 at 2:43

Thanks for the response. I would like the nodes to be externally accessible (be able to take inbound is what I'm talking about), in which case does that change anything about your answer? And I don't want a connection between both of my two local nodes, sorry if that part wasn't clear.

– SRMR
Nov 29 '18 at 22:16

You will have to run one of the nodes on a different p2p port than 8333. This is perfectly fine, since getaddr will advertise your ip address anlong with the port. One thing you should to is either use UPNP or specify the external address using the "bind" option and take care of the NAT tables in your router yourself. Otherwise the node will only know its local LAN address, flag it as "not accessible" and not broadcast your address at all; that would mean that even if your node is externally accessible, nobody would access it!

– Skriptkiddie
Nov 29 '18 at 22:35

Cool, thanks for the explanation! I will give it a try!

– SRMR
Nov 30 '18 at 2:43

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Btukfyl