Ban Bitcoin XT connections to my node?

jonald_fyookball

legendary

Activity: 1302

Merit: 1008

Core dev leaves me neg feedback #abuse #political

Quote from: erik777 on September 12, 2015, 05:36:05 PM

Quote from: unamis76 on September 12, 2015, 04:44:09 PM

Let's all ban XT connections... Then all XT users ban all Core connections, and XT and Core only connect to peers similar to them...

People are building on solutions to improve Bitcoin, trying to develop the best of both worlds and people keep on separating everything. Looks like that even people invested in Bitcoin want to ruin it deliberately which is wierd. Especially when both clients transmit pretty much the same thing and it's not possible to deploy any fork whatsoever...

This isn't war, it's trying to reach a consensus, banning each other stops consensus

75% isn't consensus. if achieved, checkpoints can be used by XT effectively force that 75% to treat it as a consensus.

if XT wanted consensus, they wouldn't consider anything under 95%.

No checkpoints needed. If more than 51% of the mining power mines bigger blocks, that's the way it will be.

erik777

sr. member

Activity: 504

Merit: 250

Earn with impressio.io

Quote from: unamis76 on September 12, 2015, 04:44:09 PM

Let's all ban XT connections... Then all XT users ban all Core connections, and XT and Core only connect to peers similar to them...

People are building on solutions to improve Bitcoin, trying to develop the best of both worlds and people keep on separating everything. Looks like that even people invested in Bitcoin want to ruin it deliberately which is wierd. Especially when both clients transmit pretty much the same thing and it's not possible to deploy any fork whatsoever...

This isn't war, it's trying to reach a consensus, banning each other stops consensus

75% isn't consensus. if achieved, checkpoints can be used by XT effectively force that 75% to treat it as a consensus.

if XT wanted consensus, they wouldn't consider anything under 95%.

unamis76

legendary

Activity: 1512

Merit: 1012

Let's all ban XT connections... Then all XT users ban all Core connections, and XT and Core only connect to peers similar to them...

People are building on solutions to improve Bitcoin, trying to develop the best of both worlds and people keep on separating everything. Looks like that even people invested in Bitcoin want to ruin it deliberately which is wierd. Especially when both clients transmit pretty much the same thing and it's not possible to deploy any fork whatsoever...

This isn't war, it's trying to reach a consensus, banning each other stops consensus

VeritasSapere

hero member

Activity: 546

Merit: 500

Quote from: Holliday on September 12, 2015, 12:05:28 PM

Quote from: VeritasSapere on September 12, 2015, 10:40:40 AM

For some of the people supporting this and based on what they have said before, can you see the hypocrisy in what they are doing here?

Quote from: Holliday on September 02, 2015, 12:47:01 PM

Bad: Client tells individual which information will be shared with whom.

Good: Individual tells client which information will be shared with whom.

Let's not be intentionally obtuse and conflate the two.

It is the individual however that chooses the client. That is where the first choice lies.

Holliday

legendary

Activity: 1120

Merit: 1012

Quote from: VeritasSapere on September 12, 2015, 10:40:40 AM

For some of the people supporting this and based on what they have said before, can you see the hypocrisy in what they are doing here?

Quote from: Holliday on September 02, 2015, 12:47:01 PM

Bad: Client tells individual which information will be shared with whom.

Good: Individual tells client which information will be shared with whom.

Let's not be intentionally obtuse and conflate the two.

VeritasSapere

hero member

Activity: 546

Merit: 500

For some of the people supporting this and based on what they have said before, can you see the hypocrisy in what they are doing here?

erik777

sr. member

Activity: 504

Merit: 250

Earn with impressio.io

Zarathustra

legendary

Activity: 1162

Merit: 1004

Quote from: masterluc on September 02, 2015, 09:57:36 PM

Holy shit, they are all Russians. Putin?

Yes, Russians have been terrorized by production quotas for a long time. They want to insure themselves against their rulers:

http://bitco.in/forum/threads/gold-collapsing-bitcoin-up.16/page-12#post-392

erik777

sr. member

Activity: 504

Merit: 250

Earn with impressio.io

The00Dustin

hero member

Activity: 807

Merit: 500

Quote from: ?? on ??

Your approach only works for nodes sending the string 'Bitcoin XT'. XT nodes are currently relaying the exact same information so there's no point in block them until January 2016.

This. In the meantime, at best, you are currently weakening the network you want to support and if enough people were to do this, it could significantly increase the chance of orphaned blocks by increasing the amount of time it takes for blocks to propagate. You could also block legitimate nodes from small countries where IP addresses are shared amongst communities simply because of one "bad actor." Lastly, because I'm not familiar with ipset, I will also point out that unless that list is cleared each time you reboot and you actually reboot sometimes, you would permanently block any address that may well switch back to core in the future. More than likely none of this matters, though, I mean, hopefully the majority of node operators don't feel like shooting their own feet to spite participants in their network.

tadakaluri

hero member

Activity: 616

Merit: 500

Quote from: masterluc on September 02, 2015, 10:51:23 AM

Is there any effective way to do this?

UPDATE. Found solution.

All paths are according to CeontOS 7. If you have different distrib, change paths.

This goes to autostart:

Code:

echo "/usr/bin/ipset create bitcoinxt iphash timeout 0" >> /etc/rc.local

This goes to /etc/cron.hourly/bitcoinxt

Code:

#!/bin/bash
/bin/grep BitcoinXT /var/log/kern.log | /usr/bin/perl -e 'while (<>) { if (/SRC=(\d+\.\d+\.\d+\.\d+)/) {print "$1\n";} }' | /bin/sort | /usr/bin/uniq -u | /usr/bin/xargs -L 1 ipset -exist add bitcoinxt

Also

Code:

# chmod 755 /etc/cron.hourly/bitcoinxt

This goes to iptables

Code:

iptables -A INPUT -m set --set bitcoinxt src -j DROP
iptables -A INPUT -p tcp -m tcp --dport 8333 -m string --string "Bitcoin XT" --algo bm --to 65535 -j LOG --log-prefix "BitcoinXT" --log-level 1
iptables -A OUTPUT -m set --match-set bitcoinxt dst -j DROP

Dont forget to

Code:

/etc/init.d/iptables save

Good Study and thank you very much for the information.

masterluc

legendary

Activity: 938

Merit: 1013

156 out of 158 discovered XT nodes are using RU IP.

meono

full member

Activity: 196

Merit: 100

Quote from: masterluc on September 02, 2015, 09:57:36 PM

Holy shit, they are all Russians. Putin?

Holy shit, your logic is astounding.

masterluc

legendary

Activity: 938

Merit: 1013

Holy shit, they are all Russians. Putin?

ipset list | grep timeout | awk '{ print $1;}' | xargs -L1 geoiplookup

Code:

GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: GB, United Kingdom
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: US, United States
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation
GeoIP Country Edition: RU, Russian Federation

meono

full member

Activity: 196

Merit: 100

Quote from: masterluc on September 02, 2015, 09:41:55 PM

Quote from: LiteCoinGuy on September 02, 2015, 12:39:24 PM

to ban it is very silly.

i recommend this podcast with gavin:

https://epicenterbitcoin.com/podcast/094/

Mike Hole likes blacklists. I see blacklist is his secret sex dream. "Oh, hunny, I was a bad boy, so please blacklist me now hard!". So here is some pleasure for him.

Code:

[root@localhost ~]# ipset list
Name: bitcoinxt
Type: hash:ip
Header: family inet hashsize 1024 maxelem 65536 timeout 0
Size in memory: 12748
References: 2
Members:
178.207.212.77 timeout 0
46.48.207.254 timeout 0
178.204.21.37 timeout 0
92.37.157.208 timeout 0
178.204.116.214 timeout 0
94.241.1.185 timeout 0
5.143.81.49 timeout 0
46.158.180.252 timeout 0
109.184.237.27 timeout 0
77.94.122.122 timeout 0
95.53.114.28 timeout 0
85.192.134.21 timeout 0
176.51.132.64 timeout 0
178.207.253.99 timeout 0
95.70.123.241 timeout 0
188.114.8.99 timeout 0
5.138.247.242 timeout 0
109.184.91.19 timeout 0
95.70.33.86 timeout 0
178.67.165.114 timeout 0
178.68.221.168 timeout 0
109.147.229.121 timeout 0
188.18.250.20 timeout 0
73.182.147.206 timeout 0
31.163.112.63 timeout 0
78.37.63.25 timeout 0
78.37.54.48 timeout 0
2.60.135.235 timeout 0
178.68.133.169 timeout 0
95.106.143.65 timeout 0
178.68.142.70 timeout 0
92.37.194.165 timeout 0
188.16.14.188 timeout 0
78.29.90.8 timeout 0
77.51.69.128 timeout 0
87.251.114.145 timeout 0
95.52.18.154 timeout 0
95.37.84.223 timeout 0
37.21.92.223 timeout 0
212.55.111.19 timeout 0
46.159.19.194 timeout 0
95.165.205.145 timeout 0
81.4.200.111 timeout 0
5.139.81.44 timeout 0
176.52.116.178 timeout 0
93.177.56.235 timeout 0
92.101.10.32 timeout 0
31.162.118.16 timeout 0
95.189.43.240 timeout 0
178.67.14.238 timeout 0
37.76.186.17 timeout 0
46.159.34.2 timeout 0
31.180.69.181 timeout 0
178.46.37.7 timeout 0
31.180.219.230 timeout 0
109.184.96.96 timeout 0
95.70.106.211 timeout 0
178.204.154.56 timeout 0
46.48.178.70 timeout 0
93.120.185.96 timeout 0
82.140.209.7 timeout 0
188.18.202.245 timeout 0
5.143.42.201 timeout 0
94.245.183.162 timeout 0
95.71.253.245 timeout 0
31.23.71.137 timeout 0
31.181.32.8 timeout 0
37.21.3.213 timeout 0
92.37.131.121 timeout 0
37.21.36.108 timeout 0
5.138.104.148 timeout 0
95.53.27.158 timeout 0
178.67.190.175 timeout 0
92.37.204.174 timeout 0
46.158.195.130 timeout 0
95.37.177.142 timeout 0
92.37.173.6 timeout 0
178.207.75.108 timeout 0
93.92.182.26 timeout 0
31.23.175.53 timeout 0
213.129.51.145 timeout 0
109.187.248.91 timeout 0
5.139.146.38 timeout 0
89.109.10.241 timeout 0
95.37.186.63 timeout 0
178.44.204.95 timeout 0
109.184.156.211 timeout 0
46.158.82.72 timeout 0
178.129.217.51 timeout 0
95.70.96.99 timeout 0
78.36.75.57 timeout 0
5.138.13.94 timeout 0
85.173.94.70 timeout 0
92.37.178.117 timeout 0
31.181.255.235 timeout 0
31.23.40.6 timeout 0
92.37.155.69 timeout 0
178.64.132.207 timeout 0
178.65.109.38 timeout 0
95.188.224.224 timeout 0
178.65.133.185 timeout 0
86.102.161.110 timeout 0
176.100.71.189 timeout 0
31.181.127.200 timeout 0
46.48.156.116 timeout 0
95.37.59.128 timeout 0
95.55.234.36 timeout 0
178.65.190.83 timeout 0
86.102.23.117 timeout 0
95.72.178.140 timeout 0
95.52.163.203 timeout 0
178.44.216.148 timeout 0
31.181.9.247 timeout 0
95.54.209.136 timeout 0
213.129.42.244 timeout 0
95.84.41.233 timeout 0
31.23.69.31 timeout 0
195.78.126.113 timeout 0
178.46.121.141 timeout 0
109.127.174.49 timeout 0
95.37.142.84 timeout 0
92.127.82.46 timeout 0
37.23.114.199 timeout 0
95.55.247.49 timeout 0
37.76.160.71 timeout 0
109.184.84.174 timeout 0
92.101.103.218 timeout 0
95.152.58.92 timeout 0
46.158.133.40 timeout 0
95.188.215.250 timeout 0
5.143.41.240 timeout 0
176.51.218.19 timeout 0
92.49.177.97 timeout 0
95.110.78.36 timeout 0
31.180.212.39 timeout 0
95.84.13.60 timeout 0
5.139.139.154 timeout 0
93.124.118.209 timeout 0
188.17.228.32 timeout 0
178.205.238.115 timeout 0
178.44.210.245 timeout 0
95.71.203.201 timeout 0
188.120.62.217 timeout 0
87.225.64.104 timeout 0

Man you need to take your meds. Also dont bother with humor again, you just suck. I can see you must be very popular at parties......

masterluc

legendary

Activity: 938

Merit: 1013

Quote from: LiteCoinGuy on September 02, 2015, 12:39:24 PM

to ban it is very silly.

i recommend this podcast with gavin:

https://epicenterbitcoin.com/podcast/094/

Mike Hole likes blacklists. I see blacklist is his secret sex dream. "Oh, hunny, I was a bad boy, so please blacklist me now hard!". So here is some pleasure for him.

Code:

[root@localhost ~]# ipset list
Name: bitcoinxt
Type: hash:ip
Header: family inet hashsize 1024 maxelem 65536 timeout 0
Size in memory: 12748
References: 2
Members:
178.207.212.77 timeout 0
46.48.207.254 timeout 0
178.204.21.37 timeout 0
92.37.157.208 timeout 0
178.204.116.214 timeout 0
94.241.1.185 timeout 0
5.143.81.49 timeout 0
46.158.180.252 timeout 0
109.184.237.27 timeout 0
77.94.122.122 timeout 0
95.53.114.28 timeout 0
85.192.134.21 timeout 0
176.51.132.64 timeout 0
178.207.253.99 timeout 0
95.70.123.241 timeout 0
188.114.8.99 timeout 0
5.138.247.242 timeout 0
109.184.91.19 timeout 0
95.70.33.86 timeout 0
178.67.165.114 timeout 0
178.68.221.168 timeout 0
109.147.229.121 timeout 0
188.18.250.20 timeout 0
73.182.147.206 timeout 0
31.163.112.63 timeout 0
78.37.63.25 timeout 0
78.37.54.48 timeout 0
2.60.135.235 timeout 0
178.68.133.169 timeout 0
95.106.143.65 timeout 0
178.68.142.70 timeout 0
92.37.194.165 timeout 0
188.16.14.188 timeout 0
78.29.90.8 timeout 0
77.51.69.128 timeout 0
87.251.114.145 timeout 0
95.52.18.154 timeout 0
95.37.84.223 timeout 0
37.21.92.223 timeout 0
212.55.111.19 timeout 0
46.159.19.194 timeout 0
95.165.205.145 timeout 0
81.4.200.111 timeout 0
5.139.81.44 timeout 0
176.52.116.178 timeout 0
93.177.56.235 timeout 0
92.101.10.32 timeout 0
31.162.118.16 timeout 0
95.189.43.240 timeout 0
178.67.14.238 timeout 0
37.76.186.17 timeout 0
46.159.34.2 timeout 0
31.180.69.181 timeout 0
178.46.37.7 timeout 0
31.180.219.230 timeout 0
109.184.96.96 timeout 0
95.70.106.211 timeout 0
178.204.154.56 timeout 0
46.48.178.70 timeout 0
93.120.185.96 timeout 0
82.140.209.7 timeout 0
188.18.202.245 timeout 0
5.143.42.201 timeout 0
94.245.183.162 timeout 0
95.71.253.245 timeout 0
31.23.71.137 timeout 0
31.181.32.8 timeout 0
37.21.3.213 timeout 0
92.37.131.121 timeout 0
37.21.36.108 timeout 0
5.138.104.148 timeout 0
95.53.27.158 timeout 0
178.67.190.175 timeout 0
92.37.204.174 timeout 0
46.158.195.130 timeout 0
95.37.177.142 timeout 0
92.37.173.6 timeout 0
178.207.75.108 timeout 0
93.92.182.26 timeout 0
31.23.175.53 timeout 0
213.129.51.145 timeout 0
109.187.248.91 timeout 0
5.139.146.38 timeout 0
89.109.10.241 timeout 0
95.37.186.63 timeout 0
178.44.204.95 timeout 0
109.184.156.211 timeout 0
46.158.82.72 timeout 0
178.129.217.51 timeout 0
95.70.96.99 timeout 0
78.36.75.57 timeout 0
5.138.13.94 timeout 0
85.173.94.70 timeout 0
92.37.178.117 timeout 0
31.181.255.235 timeout 0
31.23.40.6 timeout 0
92.37.155.69 timeout 0
178.64.132.207 timeout 0
178.65.109.38 timeout 0
95.188.224.224 timeout 0
178.65.133.185 timeout 0
86.102.161.110 timeout 0
176.100.71.189 timeout 0
31.181.127.200 timeout 0
46.48.156.116 timeout 0
95.37.59.128 timeout 0
95.55.234.36 timeout 0
178.65.190.83 timeout 0
86.102.23.117 timeout 0
95.72.178.140 timeout 0
95.52.163.203 timeout 0
178.44.216.148 timeout 0
31.181.9.247 timeout 0
95.54.209.136 timeout 0
213.129.42.244 timeout 0
95.84.41.233 timeout 0
31.23.69.31 timeout 0
195.78.126.113 timeout 0
178.46.121.141 timeout 0
109.127.174.49 timeout 0
95.37.142.84 timeout 0
92.127.82.46 timeout 0
37.23.114.199 timeout 0
95.55.247.49 timeout 0
37.76.160.71 timeout 0
109.184.84.174 timeout 0
92.101.103.218 timeout 0
95.152.58.92 timeout 0
46.158.133.40 timeout 0
95.188.215.250 timeout 0
5.143.41.240 timeout 0
176.51.218.19 timeout 0
92.49.177.97 timeout 0
95.110.78.36 timeout 0
31.180.212.39 timeout 0
95.84.13.60 timeout 0
5.139.139.154 timeout 0
93.124.118.209 timeout 0
188.17.228.32 timeout 0
178.205.238.115 timeout 0
178.44.210.245 timeout 0
95.71.203.201 timeout 0
188.120.62.217 timeout 0
87.225.64.104 timeout 0

Carlton Banks

legendary

Activity: 3430

Merit: 3080

Quote from: frontdenplastic on September 02, 2015, 06:04:45 PM

Quote from: Carlton Banks on September 02, 2015, 04:06:10 PM

Quote from: ?? on ??

Your approach only works for nodes sending the string 'Bitcoin XT'. XT nodes are currently relaying the exact same information so there's no point in block them until January 2016.

Quote from: masterluc on September 02, 2015, 10:51:23 AM

Code:

# chmod 755

I appreciate the mention.

chmod 755 does for some reason often feel like the answer to everything

No, chmod 777 is a much more powerful solution to permissioning issues.

Both are inadvisable in a root account/Mandatory Access Control system, chmod 777 in particular; the 3rd '7' will make the file or directory readable, writable and executable for Others. Other is the most sensitive access level, that's the rest of the internet that can address your IP.

TransaDox

full member

Activity: 219

Merit: 102

Quote from: masterluc on September 02, 2015, 07:32:01 PM

Quote from: TransaDox on September 02, 2015, 06:39:15 PM

All that cryptic text and command output reminds me of Windows 95. Grin

Shell driven Microsoft OS appeared only in 2009. It should remind you windows 7.

Shell driven OS's are 1960/70's technology which was extended in the 1980/90s by bolting GUIs on top. Windows 3.1 and windows 95 were GUIs on top of a DOS prompt the same way Unity, X-Windows et. al. sits on top of Bash.

If you have to go to a command prompt in Windows 7, you're probably from Linux and regressing to your inner cavemen. Cheesy

-------------------------------

On the subject of banning - generally rather than owner maintained lists. End user software shouldn't ban anything, IMO. Rate limit, yes. Drop connections, yes. Ban? No. A ban is like self harm - you are DOSsing yourself. It was a bitcoin ban mechanism that meant a Tor protected client could be encircled and de-anonmised.

Quote

In this phase, the attacker exploits the built-in Bitcoin anti-
Dos protection. The attacker chooses a non-attacker’s Bitcoin
peer and a non-attacker’s Tor Exit, builds a circuit through
this Exit node and sends a malformed message to the chosen
Bitcoin peer (e.g. a malformed coinbase transaction which is
60 bytes in size and which causes the immediate ban for 24
hours).

Sores.

erik777

sr. member

Activity: 504

Merit: 250

Earn with impressio.io

Quote from: masterluc on September 02, 2015, 12:32:14 PM

Fill in ban list

Code:

[root@localhost ~]# grep BitcoinXT /var/log/kern.log | perl -e 'while (<>) { if (/SRC=(\d+\.\d+\.\d+\.\d+)/) {print "$1\n";} }' | sort | uniq -u | xargs -L 1 ipset add bitcoinxt
[root@localhost ~]# ipset list
Name: bitcoinxt
Type: hash:ip
Header: family inet hashsize 1024 maxelem 65536 timeout 0
Size in memory: 8588
References: 1
Members:
95.52.18.154 timeout 0
31.162.118.16 timeout 0
188.18.202.245 timeout 0
92.37.204.174 timeout 0
92.37.173.6 timeout 0
95.37.186.63 timeout 0
86.102.161.110 timeout 0
178.44.216.148 timeout 0
195.78.126.113 timeout 0
92.49.177.97 timeout 0

This one should be done periodically

Code:

grep BitcoinXT /var/log/kern.log | perl -e 'while (<>) { if (/SRC=(\d+\.\d+\.\d+\.\d+)/) {print "$1\n";} }' | sort | uniq -u | xargs -L 1 ipset add bitcoinxt

Now you just need to fork XT's DoS patch, and create a patch that replaced Hearn's Tor blacklist with code that pulls from this. hahaha

erik777

sr. member

Activity: 504

Merit: 250

Earn with impressio.io

Quote from: masterluc on September 02, 2015, 11:59:35 AM

Fuck the windows.

Okay, I put this:

Code:

iptables -A INPUT -p tcp -m tcp --dport 8333 -m string --string "Bitcoin XT" --algo bm --to 65535 -j LOG --log-prefix "BitcoinXT" --log-level 1

Now need a way to extract logged IP and put it to ipset

Got log entry, found asshole 188.18.202.245

Code:

BitcoinXTIN=eth0 OUT= MAC=XXX SRC=188.18.202.245 DST=XXMYIPXX LEN=172 TOS=0x00 PREC=0x00 TTL=56 ID=64279 DF PROTO=TCP SPT=35311 DPT=8333 WINDOW=2840 RES=0x00 ACK PSH URGP=0

lol

Topic: Ban Bitcoin XT connections to my node? (Read 2747 times)