Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 836. (Read 4382671 times)

Good point. Servers were located in OVH/France until yesterday. I move machines to OVH from Linode after previous DDoS attacks year ago. These days,  sales representative at OVH promised me that they'll actively help me with DDoS attacks, because they have great infrastructure and skilled admins.

The reality of recent days was that they were even worse than Linode guys, because at Linode I was able to create multiple machines dynamically and mitigate DDoS by moving pool around many IPs. In OVH I had multicore machines with dozen of IPs, and I was prepared to mitigate DDoS by filtering the traffic by strong hardware and by routing traffic all around many of private IPs.

But.

These idiots at OVH blocked ALL these IPs at once since attacks started, claiming that the attack is affecting other customers. So I paid overpriced infrastructure for many months just for *nothing*. The only "solution" they offered me were Cisco firewalls, able to filter DDoS up to throughtput of 400 Mbit/s (excuse me??). When I rejected this offer, they simply rebooted my machines to "rescue mode", telling me that my servers are damaging their infrastructure and asking me to move my machines away.

So - never ever OVH.

Yesterday I migrated the pool to Amazon EC2, that's why the pool was completely offline for some time. I selected datacentres in USA, because they have the best infrastructure so far, and that's why you see higher latencies than "usual". But this is just a temporary problem, I'm configuring more machines around all Amazon datacentres (USA, Europe, Asia, ...) and I'm preparing smart routing algorithm, which will automatically move your miner to the closest pool endpoint.

I'm keeping all this very seriously, but it is hard to mitigate DDoS when you depend on group of impotent idiots at OVH which are able to send you only prefabricated template reports "your server is having issues, we restarted it / null routed all IPs".

Good point, I'm going to recalculate these rounds with proportional method, which gives people more fair rewards in case of pool downtime...

the tracert data below

<sup>stratum.bitcoin.cz [54.214.10.101]
  1     1 ms     1 ms     1 ms  192.168.1.1 [192.168.1.1]
  2    20 ms    20 ms    20 ms  ...pool.ukrtel.net [...]
  3    20 ms    20 ms    20 ms  10.50.19.66 [10.50.19.66]
  4    81 ms    44 ms    45 ms  xe-11-0-0.bar1.Budapest1.Level3.net [212.162.26.1]
  5   212 ms   214 ms   212 ms  4.69.141.250
  6   216 ms   217 ms   217 ms  ae-93-93.csw4.Frankfurt1.Level3.net [4.69.163.14]
  7   218 ms   218 ms   217 ms  ae-91-91.ebr1.Frankfurt1.Level3.net [4.69.140.13]
  8   213 ms   214 ms   213 ms  ae-45-45.ebr2.Paris1.Level3.net [4.69.143.134]
  9   214 ms   214 ms   214 ms  ae-43-43.ebr2.Washington1.Level3.net [4.69.137.58]
 10   216 ms   217 ms   216 ms  ae-5-5.ebr2.Washington12.Level3.net [4.69.143.222]
 11   217 ms   217 ms   221 ms  ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
 12   217 ms   217 ms   217 ms  ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
 13   214 ms   217 ms   224 ms  ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
 14   213 ms   213 ms   212 ms  ae-2-2.ebr2.Seattle1.Level3.net [4.69.132.53]
 15   390 ms   217 ms   313 ms  ae-21-52.car1.Seattle1.Level3.net [4.69.147.163]
 16   212 ms   211 ms   212 ms  AMAZON.COM.car1.Seattle1.Level3.net [4.53.144.74]
 17   211 ms   212 ms   211 ms  205.251.225.22
 18   222 ms   222 ms   240 ms  205.251.232.105
 19   225 ms   225 ms   267 ms  205.251.232.213
 20   220 ms   261 ms   226 ms  205.251.232.225
 21   218 ms   218 ms   220 ms  ec2-50-112-0-191.us-west-2.compute.amazonaws.com [50.112.0.191]
...



stratum3.bitcoin.cz [54.214.10.134]
  1     1 ms     1 ms     1 ms  192.168.1.1 [192.168.1.1]
  2    20 ms    22 ms    20 ms  ...pool.ukrtel.net [...]
  3    21 ms    19 ms    20 ms  10.50.19.66 [10.50.19.66]
  4    41 ms    41 ms    42 ms  dialup-212.162.26.85.frankfurt1.mik.net [212.162.26.85]
 5   212 ms   211 ms   212 ms  4.69.141.250
  6   217 ms   217 ms   217 ms  ae-93-93.csw4.Frankfurt1.Level3.net [4.69.163.14]
  7   217 ms   217 ms   217 ms  ae-91-91.ebr1.Frankfurt1.Level3.net [4.69.140.13]
  8   213 ms   212 ms   212 ms  ae-45-45.ebr2.Paris1.Level3.net [4.69.143.134]
  9   213 ms   214 ms   213 ms  ae-43-43.ebr2.Washington1.Level3.net [4.69.137.58]
 10   213 ms   214 ms   214 ms  ae-5-5.ebr2.Washington12.Level3.net [4.69.143.222]
 11   215 ms   215 ms   215 ms  ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
 12   214 ms   215 ms   214 ms  ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
 13   213 ms   215 ms   212 ms  ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
 14   210 ms   210 ms   211 ms  ae-2-2.ebr2.Seattle1.Level3.net [4.69.132.53]
 15   313 ms   251 ms   301 ms  ae-21-52.car1.Seattle1.Level3.net [4.69.147.163]
 16   209 ms   208 ms   208 ms  AMAZON.COM.car1.Seattle1.Level3.net [4.53.144.74]
 17   210 ms   210 ms   210 ms  205.251.225.20
 18   219 ms   219 ms   218 ms  205.251.232.103
 19   216 ms   216 ms   217 ms  205.251.232.207
 20   218 ms   217 ms   218 ms  205.251.232.225
 21   217 ms   215 ms   215 ms  ec2-50-112-0-191.us-west-2.compute.amazonaws.com [50.112.0.191]</sup>

11K shares were rewarded by 0.00000000 btc. thanks to ddos and slush's score system

17543   2013-04-17 22:22:53   11:52:18   17980185   10954   0.00000000   none   231873   25.39776000

That is potentially embezzlement; a felony in many countries.  Have fun with that....

not slush, and yea that is important.  you may want to open a dos shell or ubuntu ( spelling?? ) equivalent of tracert
In windows start > run > cmd ( open a DOS prompt ) and type tracert IP ( where IP is the address not the port of the server )

example window would look similar to this:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\nybbler905>tracert stratum3.bitcoin.cz


Tracing route to stratum3.bitcoin.cz [54.214.10.134]
over a maximum of 30 hops:

  1     8 ms    13 ms    12 ms  [ removed in copy and paste ]
  2     8 ms     7 ms    11 ms   [ removed in copy and paste ]
  3     8 ms     7 ms     7 ms    [ removed in copy and paste ]
  4    18 ms    31 ms    23 ms  rc3wt-ge10-0-0.wa.shawcable.net [66.163.76.217]

  5    23 ms    14 ms    11 ms  paix01-sea4.amazon.com [198.32.134.41]
  6    35 ms    32 ms    21 ms  205.251.225.198
  7    21 ms    19 ms    19 ms  205.251.232.90
  8    23 ms    24 ms    24 ms  205.251.232.151



where ever there is high numbers is where the issue is and there may be nothing you can do about it after the first 2-4 ' hops ' from your pc.  The first few are your ISP's connections so you could call and complain.
try it on all 3 stratum servers since anything can actualy slow one of them and not show on the others even if they are all 3 in the same box.
Along time ago i was phone support for HP/Compaq as well as Comcast ( which blows in my opinion ) so I have seen ISPs throttling specific names causing issues.  One customer could load yahoo.ca and not yahoo.com and they both are basically in the same box as an example.

Hope this helps and on a side note GOOD WORK Slush!!! I may be CPU mining, but at least i'm not solo mining!

Looks like stratum is back up, thanks for the hard work!

I recently switched to your pool from BTC Guild and wouldn't mind some trusted miner program if you decide to implement.

wtf - ddos is all they got? 

         This is dumb...

Keep up the great work slush!

Slush, you are great ! many thanks!!!

just the question... using mining_proxy-1.5.2 without any optional arguments... before APR 16 i saw access time [73ms] [78ms]... today [213ms]...[234ms]... is it important ?

+1000

And he EARNS the fee!  You think servers and bandwidth and time spent managing and tweaking the software are free.  The fee is nothing compared to the service received.  And he has worked tirelessly when the problem occurred - have had to deal with situations like this myself.  He is earning it.

You are and have been always free to switch to another pool..  don't let the door hit you in the butt on the way out...

There are 7-11 of them ignoring me ! They seem to be multiplying exponentially.

gl with the recovery, Slush.

Damn those DDOS'n inbred banksters.

pEACe

Can't trust anyone these days, can you?

I cannot believe that in every small group of people there's at least one idiot.

Can anyone help me get the stratum-mining-proxy setup to allow outside connections go through?

Trying to use a work PC to mine and my work place has a firewall, so I thought that it might be nice if I were able to use the mining proxy to get by it.

Because even though there is a 2% fee he still uses his time on this and he doesn't have to. He could just mine for another pool or anything that he wanted to do. With everyone breathing down his throat I thought maybe it would be nice to let him know that some one else appreciates his time and effort that he puts in to this.

Actually the server's down again, and you'll eventually get DC'd anyway.

Let's not forget slush charges a fee to use his pool, this isn't some charity case.  Why all the ass-kissing?

Slush you are the man I was able to get in and I've started hashing again. Thank you for your continued hard work!!!

im not managing any connection why did they hit slushes pool

I'm still getting shares from stratum3 on miner1, but miner2 connected too late apparently. 

Mining on HHTT from miner2