Bitcoin Forum
June 03, 2020, 01:43:05 PM *
News: Latest Bitcoin Core release: 0.19.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Feature Request: Limiting Connections  (Read 10352 times)
lachesis
Full Member
***
Offline Offline

Activity: 210
Merit: 100


View Profile
June 29, 2010, 12:41:52 AM
 #1

I'd like to see an option (with an RPC interface as well) to limit the number of connections that a Bitcoin client accepts. My home client is connected to 70 different nodes and my poor wimpy router just can't keep up. It's starting to slow my network down, to the point where I'll need to force Bitcoin to ignore connection requests (with -connect=<a node>) if this keeps up.

A connection limiting option would be a great alternative.

Bitcoin Calculator | Scallion | GPG Key | WoT Rating | 1QGacAtYA7E8V3BAiM7sgvLg7PZHk5WnYc
AWARD-WINNING
CRYPTO CASINO
ASKGAMBLERS
PLAYERS CHOICE 2019
PROUD
PARTNER OF
1500+
GAMES
2 MIN
CASH-OUTS
24/7
SUPPORT
100s OF
FREE SPINS
PLAY NOW
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1591191785
Hero Member
*
Offline Offline

Posts: 1591191785

View Profile Personal Message (Offline)

Ignore
1591191785
Reply with quote  #2

1591191785
Report to moderator
Vasiliev
Newbie
*
Offline Offline

Activity: 55
Merit: 0


View Profile
June 29, 2010, 01:19:51 AM
 #2

Unforward port 8333 Tongue
It'll limit it to 15 and still work fine.
lachesis
Full Member
***
Offline Offline

Activity: 210
Merit: 100


View Profile
June 29, 2010, 01:52:47 AM
 #3

Alright. Thanks.

Would still be a nice feature. I don't mind people connecting to me to bootstrap or something, and I'd probably leave it at 40 rather than 15.

Bitcoin Calculator | Scallion | GPG Key | WoT Rating | 1QGacAtYA7E8V3BAiM7sgvLg7PZHk5WnYc
BitcoinFX
Legendary
*
Offline Offline

Activity: 2142
Merit: 1373


dailymotion.com/video/x5xu080 - 28:00


View Profile WWW
June 30, 2010, 01:54:04 AM
 #4

Might I 2nd this request as a 'standard' GUI feature.

I've recently tested bitcoin through various socks proxies / providers and the ability to limit connections below 10 would be really useful.   

Guess I'm a Genuine "Bitcoin OG" <2010 | Bitcoin is BTC | CSW is NOT Satoshi Nakamoto | I Mine BTC, LTC, ZEC, XMR and GAP | Support my BTC on Tor addnodes Project ... satofxsc3xjadxsm.onion shindo45rxrk3737.onion naka7nzsu3binfim.onion motoixfjxnf4joga.onion | "Everybody's Got Something to Hide Except Me and My Monkey"
satoshi
Founder
Sr. Member
*
qt
Offline Offline

Activity: 364
Merit: 2568


View Profile
July 02, 2010, 07:21:36 PM
 #5

Thanks for the feedback on this.

One thing we could do is lower the outbound connections from 15 to 10 or maybe even 5.  The choice of 15 was arbitrary.  It just needs to be enough for redundancy and fast exponential propagation of messages.  10 would still be plenty.  5 should be fine.  10 is good as a nice round number so users can see that it stopped intentionally.

It would help to implement UPnP so there would be more inbound accepting nodes.  Your number of connections is the ratio of inbound accepting nodes to out-only times 15.  We need to encourage more people to accept inbound connections.

I will implement a feature to stop accepting inbound connections once you hit a certain number.

Which version are you running?

Anyone know how many connections typical P2P software like BitTorrent can get up to?

laszlo
Full Member
***
Offline Offline

Activity: 199
Merit: 480


View Profile
July 02, 2010, 07:33:24 PM
 #6

BitTorrent clients can do hundreds of connections easily - this is why they end up killing those little embedded routers.  It should be no problem for a regular IP router but the little embedded things are doing NAT so they're tracking state on all those connections and run out of memory.. also they're very slow SoC style computers so everything going through them suffers.

Torrent clients generally have options for configuring a global maximum number of connections, maximum inbound and maximum outbound connections.

I think it would be good to allow configuration of unlimited inbound/outbound connections for those who have the capability to do it, and provide a conservative default for those who are using NAT, tor, proxies, etc.

BC: 157fRrqAKrDyGHr1Bx3yDxeMv8Rh45aUet
satoshi
Founder
Sr. Member
*
qt
Offline Offline

Activity: 364
Merit: 2568


View Profile
July 02, 2010, 10:20:20 PM
Last edit: July 02, 2010, 10:33:43 PM by satoshi
 #7

I reduced max outbound connections from 15 to 8 in RC4.

15 was way more than we needed for redundancy.  8 is still plenty of redundancy.

As the nodes upgrade to this version, this will cut in half the number of connections that inbound accepting nodes get.

If anyone wants more than 8 connections, they can open port 8333 on their firewall.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!