Re: [25+PH] Kano CKPool kano.is 0.9% PPLNS US,DE,SG,JP,NL,NYA

Latest update of the miner all time stats (since May 2016)

Code:

CDF[Erl] | Miner | DiffAcc
0.997872 | S9v1 | 27,650.93G | 112.59655135 BDR | 84 Blocks
0.798780 | A7v2 | 513.85G | 1.60335652 BDR | 1 Block
0.531652 | A7v1 | 2,851.43G | 9.91705950 BDR | 10 Blocks
0.167142 | S9v2 | 5,683.25G | 19.28094844 BDR | 24 Blocks

All OK as usual ... except S9v1 Tongue

Not a single block from any of the new R4's?
Wonder how many R4's are in live the pool?
Mine has been hashing away for almost a month now. Hope it finds a block for us soon.
Thanks for the update.

That's a good point! No R4's have found a block yet on the pool..

They probably fall under S9v2 - bitmain don't say "S9" they just say the version of their fork.
So they are probably S9v2 - if someone wants to tell me a worker that is only R4 I can check to see what they call themselves.

My only miner is an R4 B2.
Worker Name: wblaster.antMiner_R4_mab

OK, that shows the same firmware as S9v2 - so I'll mark that from now on as S9v2+R4v2

Yeah...
Yesterday I was just helping a friend to repair his broken S9 (I do not know which revision the crap was) and i was looking at tcpdump in my router to see what S9 is doing....And Guess what....S9 is Sending !!!!unatended!!!! ICP destination host unreachable with a pay load something like json data to X IP. Then X IP responds back WITH UDP and payload something like json data. Sounds familiar Wink

There are a lots of ICMP and UDP packets coming in/out S9 miner to UNKNOWN IP's containing guess what Grin

The funny part is that S9 controller is custom made with special HW and there is no way someone to put customised FW inside it except BITMAIN. So i guess this incredible feature is BY design. The other funny part is that you have to wait this shit for 10 mins or so while ASICS are warming up Grin

Pathetic. Meanwhile the mentioned UDP/ICMP are going in and out like creasy. Probably to help to warming up process Grin

More Over after warming up process finishes UDP/ICMP DO CONTINUE TO COME IN AND OUT
So ... If in doubt EVERYONE CAN CHECK THIS BY HIMSELF
I am just wandering how that fact remained in secret having in mind how many folks have them in their hands Huh

It is just one minute to fire a tcpdump and see what is going on.
A clean and healthy miner behaviour is:

1 UDP DNS requests to resolve pool ip and NTP IP
2. Sync TIME - UDP to NTP servers
3. Start to MINE TCP ONLY!
4. Repeat one and two
5. MINE TCP ONLY

Is this really happening on the S9's?
I'm a noob to mining, but as an IT person, (if the above is true) shouldn't this be something to investigate?