Topic: If I am running a node can I make it two? (Read 1224 times)
my net is 50/15, but I do not do much video conferencing.
Unless you have a complete potato internet i.e you have trouble refreshing this page, you are more than fine on bandwidth.
Some beg to differ:
nullc / gmaxwell:
Quote
On bandwidth, it really is a problem for many users. For buffer bloat affected routers it Bitcoin Core currently makes your internet connection completely unusable periodically, multiple second ping times that kill web loads and knock out VoIP-- even when you are outbound only. After moving to silicon valley and finding myself inflicted with DSL instead of the nice FiOS I had back east, I've intentionally not fixed the problem (by sticking a FQ-CoDeL linux router in front of the DSL modem) for myself at home (because only ultra geeks will use that fix and I want to experience what other people experience), but it's gruesome and I have to turn off Bitcoin during conference calls. (This is also actually a problem on my offices newly installed 160/30mbit comcast service).
https://www.reddit.com/r/Bitcoin/comments/37vsh4/interview_with_gavin_andresen_and_peter_todd_on/crqlxfc
Well I built the dedicated node and it is doing pretty well burns 24 watts and all it runs is the node.
I left the wallet empty. After it runs a week I am starting a thread on how low powered an effective node can be.
This pulls 24 watts with the display powered off. I need to see if it gets up to 8.5 or more it should do so after 1 week of run time.
right now I am at 6.8
I left the wallet empty. After it runs a week I am starting a thread on how low powered an effective node can be.
This pulls 24 watts with the display powered off. I need to see if it gets up to 8.5 or more it should do so after 1 week of run time.
right now I am at 6.8
You could do that but it would not be helpful to the network since only one of them will be
able to allow incoming connections.
That's not entirely correct. You can give one of them a different port number and open that port on the router, so your two nodes share one external IP address but have different port numbers.able to allow incoming connections.
Don't know how well other nodes get along with that, though.
short answer: don't
Maybe that's still the right answer here - your home network connection probably does not have enough uploading bandwidth to support two full nodes, so they will throttle incoming connections anyway. Just staying with one node might indeed be better.
Onkel Paul
Unless you have a complete potato internet i.e you have trouble refreshing this page, you are more than fine on bandwidth.
yeah well 2 crashed and burned. So I will keep one.
I built a pc from left over gpu mining parts.
Using an i5-2500t low power cpu
an asrock h77 m pro mobo
a sataII samsung ssd 250gb
an antec plat psu
2 sticks of 4gb ram.
this will run just the bitcore and nothing else.
I turned off the better pc after loading the wallet with a few coins.
This new one loads pretty slow I am on week 27.
I built a pc from left over gpu mining parts.
Using an i5-2500t low power cpu
an asrock h77 m pro mobo
a sataII samsung ssd 250gb
an antec plat psu
2 sticks of 4gb ram.
this will run just the bitcore and nothing else.
I turned off the better pc after loading the wallet with a few coins.
This new one loads pretty slow I am on week 27.
IIRC, the recommendation is to have just one node to the outside world and all nodes on the inside network connect to that one. Different port won't help, as other clients will look for port 8333. You could consider having your one node available on TOR as well though. That way you'd have "two" nodes, one on "clearnet" and one on TOR, but of course on just one PC with a single instance of Bitcoin Core.
That's not entirely correct. You can give one of them a different port number and open that port on the router, so your two nodes share one external IP address but have different port numbers.
Don't know how well other nodes get along with that, though.
Onkel Paul
http://bitcoin.sipa.be/seeds.txt has some nods running on a port other than 8333 but they seem to be marked as bad.
I'll dig deeper in the networking code but thanks for pointing it out.
I had thought only one would work well. thanks for replies.
You could do that but it would not be helpful to the network since only one of them will be
able to allow incoming connections.
That's not entirely correct. You can give one of them a different port number and open that port on the router, so your two nodes share one external IP address but have different port numbers.able to allow incoming connections.
Don't know how well other nodes get along with that, though.
short answer: don't
Maybe that's still the right answer here - your home network connection probably does not have enough uploading bandwidth to support two full nodes, so they will throttle incoming connections anyway. Just staying with one node might indeed be better.
Onkel Paul
You could do that but it would not be helpful to the network since only one of them will be
able to allow incoming connections.
short answer: don't
able to allow incoming connections.
short answer: don't
I run a node, If I use a second pc with bt core do I 2x my node.
Or I guess I am asking with 1 ip can I run 2 nodes or does 1 bt core max the ip.
I have a node setup for a few days node and I was wondering can 2 be done one 1 ip?
Bitnodes
Or I guess I am asking with 1 ip can I run 2 nodes or does 1 bt core max the ip.
I have a node setup for a few days node and I was wondering can 2 be done one 1 ip?
Bitnodes
Jump to: