Add Linux script to contrib/ that limits outgoing bandwidth to Bitcoin nodes #2728

pull runeksvendsen wants to merge 1 commits into bitcoin:master from runeksvendsen:master changing 2 files +44 −0

runeksvendsen commented at 7:43 PM on June 2, 2013: contributor

This commit adds a Linux script that uses tc and iptables to limit outgoing bandwidth to Bitcoin nodes. All tcp connections with a source or destination port of 8333 are limited to the chosen rate. It does not alter the incoming bandwidth. Additionally, outgoing bandwidth to a host on a local LAN (192.168.x.x) is not limited.
BitcoinPullTester commented at 9:24 PM on June 2, 2013: none

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/68d0a7d5a4ba59a977966f7c8b3ed0f113ff1586 for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
petertodd commented at 9:40 PM on June 2, 2013: contributor

Thanks. The other thing to do is squash those two commits together - we don't like having excess commits in the tree without a good reason. If you aren't familiar with git look up the git-rebase command (specificially the -i interactive flag) for how to do this.

Add Linux script to limit outgoing bandwidth used by Bitcoin

This commit adds a Linux script that uses tc and iptables to
limit outgoing bandwidth to Bitcoin nodes. All tcp connections with
a source or destination port of 8333 are limited to the chosen rate.
It does not alter the incoming bandwidth. Additionally, outgoing
bandwidth to a host on a local LAN (defined by the LOCALNET variable)
is not limited.

2002bceac5

runeksvendsen commented at 10:18 AM on June 3, 2013: contributor

Done. I think I did it right. I messed up the rebase so I had to go back. But it looks right to me now.
BitcoinPullTester commented at 11:39 AM on June 3, 2013: none

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/2002bceac5b8fad593c9cf83cc4e7127029f2174 for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
jgarzik referenced this in commit a2a2874fc0 on Jun 10, 2013
jgarzik merged this on Jun 10, 2013
jgarzik closed this on Jun 10, 2013
sipa commented at 3:18 PM on June 10, 2013: member

meh
runeksvendsen commented at 3:20 PM on June 10, 2013: contributor

After speaking to sipa on #bitcoin-dev I think it would be appropriate to add a warning to the readme about the consequences of using this script. Perhaps that it's advisable to only use this script with the -nolisten option, as you otherwise risk feeding someone the blockchain really slowly.
DrahtBot locked this on Sep 8, 2021

Contributors