ButtCrack



Offline



Activity: 434

Merit: 250







Sr. MemberActivity: 434Merit: 250

Re: [ANN][CLAM] CLAMS, Proof-Of-Chain, Proof-Of-Pearl, Recent Mandatory Update November 08, 2014, 10:40:13 PM #1282 Quote from: Thirdspace on November 06, 2014, 10:03:12 PM Quote from: tryphe on November 06, 2014, 09:13:41 PM You probably want to use -addnode and not -connect, because connect implies a set exclusive peer list (i.e. you won't connect to any other peers). Or you can just remove them from the .conf after you load it, as the valid ones will now be in peers.dat

maybe that is what he intended to do... only connect to exclusive peer (that he believes on the main/correct chain)

I actually tried removing .conf after that and started the client again, and it still re-connects to certain clients on wrong fork again

I think because it always ask for more new peers from the connected peers to propagate the network

How can I tell? because when I removed .conf my upload bandwidth went crazy again...

all connected peers are all different than those exclusive list I connected earlier

and I noticed 1 of the connected peer height is way below (is at 173217) and stay like that for days as I remember

also a few connected nodes are at "startingheight" : -1 I doubt that means he just started.

What exactly height -1 means here?

in .conf file, is there a way to block certain peer? something like perma-banned until we removed it in the future

maybe that is what he intended to do... only connect to exclusive peer (that he believes on the main/correct chain)I actually tried removing .conf after that and started the client again, and it still re-connects to certain clients on wrong fork againI think because it always ask for more new peers from the connected peers to propagate the networkHow can I tell? because when I removed .conf my upload bandwidth went crazy again...all connected peers are all different than those exclusive list I connected earlierand I noticed 1 of the connected peer height is way below (is at 173217) and stay like that for days as I rememberalso a few connected nodes are atI doubt that means he just started.What exactly height -1 means here?in .conf file, is there a way to block certain peer? something like perma-banned until we removed it in the future

Its indeed intended to force your wallet to connect only to certain/trusted peers.

When using connect= , Listen=1 will be ignored, which means no incomming connects accepted.

What clam needs would be so-called seed peers or nodes.

1 is enough, but for back up reasons of course its better to have at least 2 or more.



How to block certain peers ?

You can make use of an ip filter like peerblock.

There are others out there.

Also LMHOST file inside your windows directory can be used to do that, effectively redirecting unwanted ip to blackhole, and have a nice day !

But any decent firewall, indeed NOT windows firewall, can be use to block.

Depending on what apps I have running I use firewall and at times make use of peerblock on top of it.

Peerblock comes with block lists so you can block ip ranges of anti p2p, secret service or other crap.



Also have a look at TCPView, it shows you what is connected to your box.

It has helped me findig unwanted connects of various app including Windows.

NETstat will do the same btw.



As usual, a quick search on the net should get you further information.

Do a search of bitcoin.conf to locate the wiki, detailed info about options and how to use them.



Further questions ?

Just post and I will try to help if time permits it.



Anyway time to stop I start to make stupid typos. You are spot on.Its indeed intended to force your wallet to connect only to certain/trusted peers.When using connect= , Listen=1 will be ignored, which means no incomming connects accepted.What clam needs would be so-called seed peers or nodes.1 is enough, but for back up reasons of course its better to have at least 2 or more.How to block certain peers ?You can make use of an ip filter like peerblock.There are others out there.Also LMHOST file inside your windows directory can be used to do that, effectively redirecting unwanted ip to blackhole, and have a nice day !But any decent firewall, indeed NOT windows firewall, can be use to block.Depending on what apps I have running I use firewall and at times make use of peerblock on top of it.Peerblock comes with block lists so you can block ip ranges of anti p2p, secret service or other crap.Also have a look at TCPView, it shows you what is connected to your box.It has helped me findig unwanted connects of various app including Windows.NETstat will do the same btw.As usual, a quick search on the net should get you further information.Do a search of bitcoin.conf to locate the wiki, detailed info about options and how to use them.Further questions ?Just post and I will try to help if time permits it.Anyway time to stop I start to make stupid typos.