Classic nodes being DDoSed now?

[arnoudk]

It was bound to happen. Like XT before it, classic nodes are now being DDoSed according to reddit.

https://www.reddit.com/r/btc/comments/4 ... sic_nodes/

I'm not able to check my nodes (easily) right now but I have seen no emails from my provider. Yet.

I'll be donating to classic-cloud.net all the same to spin up extra classic nodes. If this continues I might spin up a few aws nodes myself too.

If you would like to join in making a statement that DDoS will not work, also spin up some classic nodes in classic-cloud.net. Or at any provider with good DDoS protection.

Who can recommend a good host for this other than amazon?

[arnoudk]

Funding went through and the node is up and running.

I may fund another one if it is still ongoing tomorrow. This is really easy and I don't see the benefit of spending my own time given how easy it is.

[LiteCoinGuy]

DDOSing someone is always a bad move and a criminal act by the way. in my view we are on a good path to find consensus and iam confident that the core team will now listen to other opinions. Gavin, Roger, and we made this happen. Gj.

I will follow Core for the moment.

[evilroot]

I can confirm that Classic nodes has been targeted. My Classic nodes has been eating 100+Mbit/s on and off for close to 12 hours now.

It's getting slightly annoying.

[arnoudk]

Looking at nodecounter.com I see that the ddos is still ongoing.

So I funded another node in aws.

I wonder how easy it would be to do the following. Offer an aws service that checks the availability of YOUR node. If it goes down, automatically launch 10 aws nodes. When YOUR server comes back up, bring the aws nodes down again.

This makes DDoS counter productive.

[bitkilo]

Looking at nodecounter.com I see that the ddos is still ongoing.

So I funded another node in aws.

I wonder how easy it would be to do the following. Offer an aws service that checks the availability of YOUR node. If it goes down, automatically launch 10 aws nodes. When YOUR server comes back up, bring the aws nodes down again.

This makes DDoS counter productive.

Just seen this on a blockchain news feed:
http://nodecounter.com/how_to_defeat_dd ... lassic.php

Looks like your already doing the right thing, keep those extra nodes coming, good work arnoudk.

[arnoudk]

Thanks.

This DDoSing happened to me when I was running XT. I then chickened and ran XT in stealth mode (I actually implemented it before stealth mode existed). Although the node was ready for bigger blocks, it felt wrong to give in like that.

I then promised myself that if this would happen again that I would setup nodes in a datacenter that could handle an attack. My VPS provider is very useless and disables entire servers the moment a ddos packet arrives at their router.

Paying for two classic nodes in the classic cloud was the easy thing to do.

Now I am synching a aws micro instance. I wonder if it is powerful enough. We shall see. I can run these for shorter periods. Maybe I can run 10 or 20 nodes for a few weeks as long as the attack lasts and shut them down again when it stops. It would be cheaper than running nodes for multiple months in the classic cloud.. alhough that of course adds more benefit.

Does anyone know how I can use the aws monitoring to launch nodes based on the unavailability of a non aws node? I've never looked into that.

Anyway you could say I am having fun. I actually quite like the concept of firing up more nodes during an attack. I like making attacks counterproductive. I can do my part in it.

[arnoudk]

My aws micro instance has synced 28% in the last 24 hours.

The last blocks take longest to synch though. And aws micro instances have CPU credits that have been used up fully already so now it is running at approx 10% of CPU power.

I am synching with BU 12.0 because it has the faster sig validation. Maybe I should keep using it and just change the identifier to Classic/0.11.2 rather than BitcoinUnlimited/0.12. BU allows for great resource management that will make running a node more reliable and affordable.

[arnoudk]

If you look at nodecounter.com you can see that the ddos is having the exact opposite effect than what is intended.

You could not tell from the graph that the attack is still ongoing. But according to some redditors it is still ongoing. The number of nodes is actually higher now than it was before the attacks began.

Because it is still ongoing (i'll take their word for it) I have funded my third cloud node. That brings my total public nodes to 6, of which 5 are running.

If you look at classic-cloud.net you can see how much support there is! 500 extra nodes have been launched. They will have to increase capacity soon!

Why did I pay for another cloud node when I am building my own aws micro node?

Simple:
The aws micro sync is still ongoing. It will be a few more days at least before it is synced.

In my opinion, a network upgrade is too important to be sabotaged by a script kiddie. I am doing what I can to ensure bitcoin has a bright future.

[evilroot]

The DDoSing has resumed. Started 07:56 CEST on one of my Classic nodes.

[fBSDluv]

The DDoSing has resumed. Started 07:56 CEST on one of my Classic nodes.

they are mad at us because we believe in sharing, - Jihan Wu "In my opinion, Chinese culture has always longed for powerful leaders. In the west however, people are more used to competition between multiple authorities, and deem centralization as great threat. So opponents like Classic, tend to gain more sympathy in the west, but hostility in the east."

europe + america will sort it out

[arnoudk]

The DDoSing has resumed. Started 07:56 CEST on one of my Classic nodes.

Great

I wonder if my 2 new classic vps nodes will get attacked within 24 h of booting up. Guess we shall see.

[bitkilo]

So someone has owned up to doing this for pay, if true who do you think is paying, one guess
https://np.reddit.com/r/Bitcoin_Classic ... _day_guys/

[arnoudk]

So someone has owned up to doing this for pay, if true who do you think is paying, one guess
https://np.reddit.com/r/Bitcoin_Classic ... _day_guys/

That would be speculation. I would try to avoid doing that. In a strange way it makes bitcoin stronger, nodes have migrated to DDoS protected cloud services (for a part) which are a LOT harder to DDoS than home nodes. Bitcoin Classic has evolved to be more resistant to DDoS (datacenter DDoS protected nodes) while also being decentralized (many less DDoS protected nodes in many jurisdictions, on many different networks, including on home networks.)