Since I updated to 2.1 yesterday the wallet is using LOTS of network bandwidth. I let it run over night and this morning it was sending at a rate of nearly 100 kb/s. Perfmon is showing Bottlecaps connections with 5-15 kb/s. Debug log is full of getblocks. Deleting peers.dat and restarting wallet doesn't fix it. What can I do?
So there are still a few people who do not know their wallet is stuck and requesting the same blocks over and over. After the fork I am going to be sending an alert to all people on 2.0 and 2.0.0.1. Advising them to check and make sure they are on the right block and that they should upgrade to 2.1 to fix a staking issue with their client.
In the mean time you can click the connections bar and see if you have a bad peer.
You can see a bad peer as follows.
Good Peer:
Peer IP: 176.37.67.61:7685
Time Connected: 18:23:58
Time of Last Send: Fri Jun 20 15:27:10 2014
Time of Last Recv: Fri Jun 20 15:27:10 2014
Bytes Sent: 795295Bytes Recv: 838737
Blocks Requested: 1
Version: 70003
SubVersion: /Satoshi:0.7.5/
Inbound?: Y
Starting Block: 503739Ban Score(100 max): 0
Likely Bad Peer:
Peer IP: 173.192.30.91:7685
Time Connected: 03:50:13
Time of Last Send: Fri Jun 20 15:27:10 2014
Time of Last Recv: Fri Jun 20 15:24:48 2014
Bytes Sent: 123148968Bytes Recv: 7121759
Blocks Requested: 0
Version: 70003
SubVersion: /Satoshi:0.7.5/
Inbound?: Y
Starting Block: 498915Ban Score(100 max): 0
You can then ban that IP via your firewall.. I won't be doing this personally as I will be needing to send them alerts. But there is nothing to stop you from removing a peer you deem unreliable.
my wallet stock stock in block 607 im using the latest fix... where can i find the connection bar?