I can only speculate that it has to do with the miners software on those things which doesn't seem to like the pool
I 100% agree. Somehow I think its linked to that "garbage string" they seem to send to stratum (from what i've read)....
I wonder if someone compiles a fresh cgminer for them if it would fix the problem.
The strange thing is it seems to increase in severity with hashrate.
My S3's rarely saw downtime, and it was always happening on any pool anyways.
Ive heard of the S5's having issues staying connected on the pool
And worse with S7 Etc...
I wonder whats so different between your stratum and kano....
ive had good luck with the java stratum proxy..
https://github.com/Stratehm/stratum-proxysetting the proxy to use ES then NOT enable ES on the s7.
also setting a diff helps a lot..
WHAT DIFF WOULD YOU SUGGEST FOR 1-4GH/s? --
I stopped mining with my S5 units because they kept crashing on ZPOOL. I was afraid that they were being damaged. They hung-up, requiring a reboot, instead of rolling over to another pool.
My payments went from 1-1.5 DASH a day, to practically nothing. I suspected I was being paid BTC percentages applied to DASH coin, my prefered payment coin.
There are a couple spare RasPi units lying around, I may work on the proxy set-up. I've never bothered to set difference values for minning before. --scryptr
you can try starting at 2000.. just make sure you pick a number that isnt a power of two.. bitmains cgminer fork hates that for some reason and it bugs out..
so no, 1024, 2048, 4096 etc..
edit, i just noticed you said 1-4GH/s and not TH/s heh.. i read s5 and thought maybe you meant for that.. or did you??
So I corrected it. Quotes may be off, preserving my mistake for a digital eternity. --scryptr