I have same dilemma...except I have my new S9's...but the Mauser power cables from Texas are in the DHL Ottawa penalty box for two days also. BAH HUMBUG!!!!!!!
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 631. (Read 5352367 times)
December 26, 2017, 02:06:39 PM
December 26, 2017, 02:01:46 PM
This kinda sux.
3 of the 4 S9's are in my city, at the DHL center, cleared customs, and one is on plane departed Hong Kong. But what is the worst part is that DHL isn't open to allow me to pick it up today!!
Its only noon. I have time to devise a plan for extraction today! haha Any ideas?
Maybe ask RWBY Yang to come along and help you get into the building?3 of the 4 S9's are in my city, at the DHL center, cleared customs, and one is on plane departed Hong Kong. But what is the worst part is that DHL isn't open to allow me to pick it up today!!
Its only noon. I have time to devise a plan for extraction today! haha Any ideas?She seems pretty good at breaking (into) stuff with her fists
December 26, 2017, 01:42:26 PM
This kinda sux.
3 of the 4 S9's are in my city, at the DHL center, cleared customs, and one is on plane departed Hong Kong. But what is the worst part is that DHL isn't open to allow me to pick it up today!!
Its only noon. I have time to devise a plan for extraction today! haha Any ideas?
Someone joked around and said they sent them a lot sooner than the Jan 21 - 30, so they must of sent a bunch of Mandarin Oranges instead! Hope not..
3 of the 4 S9's are in my city, at the DHL center, cleared customs, and one is on plane departed Hong Kong. But what is the worst part is that DHL isn't open to allow me to pick it up today!!
Its only noon. I have time to devise a plan for extraction today! haha Any ideas?Someone joked around and said they sent them a lot sooner than the Jan 21 - 30, so they must of sent a bunch of Mandarin Oranges instead! Hope not..
December 26, 2017, 01:32:45 PM
Ah so that explains the 60Th hashrate drop alert...seems to be coming back up now.
How's that far future relative going? She got her block 
December 26, 2017, 01:27:41 PM
Thank you K, for your dedication.
Quote
Firstly, the banning is working fine, and this is the first time I've enabled this extra blocking, that already existed in the code when I first wrote it all, and it's working fine also.
This banning might ban someone, while it's active, who makes a mistake, but I think that's way better than stopping everyone logging in.
... and anyone who gets on by mistake, can always contact me to get off the ban list very quickly.
There's only been about 700 banned IPs, but I did completely block a bunch of large subnets before hand that were all bots.
Most of the previous banning has been either IP subnets that had very large numbers of bots, or simply disabling logins for a short while until they got bored having no effect on anything.
This one has sorta gone on all day, so this solution is the best in this case, in my opinion.
Lastly, most people with more than a few miners, have a different place/places for their miners.
This banning might ban someone, while it's active, who makes a mistake, but I think that's way better than stopping everyone logging in.
... and anyone who gets on by mistake, can always contact me to get off the ban list very quickly.
There's only been about 700 banned IPs, but I did completely block a bunch of large subnets before hand that were all bots.
Most of the previous banning has been either IP subnets that had very large numbers of bots, or simply disabling logins for a short while until they got bored having no effect on anything.
This one has sorta gone on all day, so this solution is the best in this case, in my opinion.
Lastly, most people with more than a few miners, have a different place/places for their miners.
December 26, 2017, 01:24:42 PM
Ah so that explains the 60Th hashrate drop alert...seems to be coming back up now.
December 26, 2017, 01:10:06 PM
Doing an immediate restart of the backend pool - it's failing to keep up with the work changes by a few seconds regularly over the past hour.
Everyone will failover and back.
Web site wont be affected
Edit: hash rate heading back up to where it was. Restart cleared up the problem. All OK again. Mine on!
Everyone will failover and back.
Web site wont be affected
Edit: hash rate heading back up to where it was. Restart cleared up the problem. All OK again. Mine on!
December 26, 2017, 01:08:56 PM
Pretty sure ol' Kano has it figured out... 
Of course. I've full confidence. I only post when I care and feel I can be additive; I appreciate the work and am happy to be part of the pool
December 26, 2017, 12:23:17 PM
Pretty sure ol' Kano has it figured out...
December 26, 2017, 12:20:49 PM
Firstly, the banning is working fine, and this is the first time I've enabled this extra blocking, that already existed in the code when I first wrote it all, and it's working fine also.
This banning might ban someone, while it's active, who makes a mistake, but I think that's way better than stopping everyone logging in.
... and anyone who gets on by mistake, can always contact me to get off the ban list very quickly.
There's only been about 700 banned IPs, but I did completely block a bunch of large subnets before hand that were all bots.
Most of the previous banning has been either IP subnets that had very large numbers of bots, or simply disabling logins for a short while until they got bored having no effect on anything.
This one has sorta gone on all day, so this solution is the best in this case, in my opinion.
Lastly, most people with more than a few miners, have a different place/places for their miners.
If the banning is happening in your apache script, perhaps you could just ban for a day. If the blocks are happening in your firewall, that also can be done but not as easily since you would have to allow the apache server to have access to the ban list and manually parse through the logs to get the time. Ok, I just read all the previous and see it is in your code and it sounds like you are doing a day. This banning might ban someone, while it's active, who makes a mistake, but I think that's way better than stopping everyone logging in.
... and anyone who gets on by mistake, can always contact me to get off the ban list very quickly.
There's only been about 700 banned IPs, but I did completely block a bunch of large subnets before hand that were all bots.
Most of the previous banning has been either IP subnets that had very large numbers of bots, or simply disabling logins for a short while until they got bored having no effect on anything.
This one has sorta gone on all day, so this solution is the best in this case, in my opinion.
Lastly, most people with more than a few miners, have a different place/places for their miners.
Personally in my code, I allow 3 attempts, then lock for 5 minutes then 15 on the next, then 60 on the next and a day one the next. I have detection for all kinds of hacker things (injection, arrays, etc) and if the server detects those, then the ip is blocked for a day. As with yours, I do most in my code although my servers also have a firewall that blocks on ssh attempts, etc. It seems that it would be good if you had something in place all the time rather than manually turning on and off your systems when threats are detected. I suspect that even you need to sleep once in a while.
This is precisely the kind of solution and motivation I meant earlier. It's up to you (Kano) how you want to manage your system as it's your time and property, but the point is not about the code quality but rather the process: As noted you can get careless humans as well as bots. Newbies may also think that UX is a bug. The manual aspect of enabling/disabling plus dealing with individuals is a side effect of that process. Automating this process is an added efficiency that should solve both UX and operational concerns. Of course that means changes to working code, and depending on the code it may not be so straightforward, I get that. Not trying to pile on or argue, but merely suggest - small manual processes add up over time, enough of those compounding take away time from getting real work (or sleep) done.
December 26, 2017, 11:07:50 AM
Time to get a few blocks in before the new year!
December 26, 2017, 10:36:59 AM
YAAAAAAAAAAAYYYYYYYYYYY!!!!!!!!!!!!!!!!!
I got the Rude awkening from DHL auto call for owing money... I was like WTF!... Not yet...
I owed them money so I paid then went, lets see - only bitmain supposed to send me stuff... Could it be.....
Log into bitmain thinking they just sent the power supply only, you know, a funny joke maybe?
NOPE!!!! They Sent ALL 4 of my S9's and power supplies! I actually got another DHL Duties and taxes call while writing this!
SOOOOO Excited!!!
EDIT: I have a voip system that can handle 25 calls to one phone - They made 3 calls at the same time, two of which went to voicemail for the duties and taxes for the other packages!
Its like CHRISTMAS on the 26th! and the 27th when they are to be delivered!
This was the Jan 21-30 Batch of S9's that I ordered! I started the orders in Nov around the 25th until first week in dec, all on different days over 2 weeks or so.
I got the Rude awkening from DHL auto call for owing money... I was like WTF!... Not yet...
I owed them money so I paid then went, lets see - only bitmain supposed to send me stuff... Could it be.....
Log into bitmain thinking they just sent the power supply only, you know, a funny joke maybe?
NOPE!!!! They Sent ALL 4 of my S9's and power supplies! I actually got another DHL Duties and taxes call while writing this!
SOOOOO Excited!!!
EDIT: I have a voip system that can handle 25 calls to one phone - They made 3 calls at the same time, two of which went to voicemail for the duties and taxes for the other packages!
Its like CHRISTMAS on the 26th! and the 27th when they are to be delivered!
This was the Jan 21-30 Batch of S9's that I ordered! I started the orders in Nov around the 25th until first week in dec, all on different days over 2 weeks or so.
December 26, 2017, 10:24:16 AM
Time for that Boxing Day block and subsequent BitGeld!
December 26, 2017, 09:50:46 AM
MINE ON!!!
December 26, 2017, 08:09:07 AM
Firstly, the banning is working fine, and this is the first time I've enabled this extra blocking, that already existed in the code when I first wrote it all, and it's working fine also.
This banning might ban someone, while it's active, who makes a mistake, but I think that's way better than stopping everyone logging in.
... and anyone who gets on by mistake, can always contact me to get off the ban list very quickly.
There's only been about 700 banned IPs, but I did completely block a bunch of large subnets before hand that were all bots.
Most of the previous banning has been either IP subnets that had very large numbers of bots, or simply disabling logins for a short while until they got bored having no effect on anything.
This one has sorta gone on all day, so this solution is the best in this case, in my opinion.
Lastly, most people with more than a few miners, have a different place/places for their miners.
If the banning is happening in your apache script, perhaps you could just ban for a day. If the blocks are happening in your firewall, that also can be done but not as easily since you would have to allow the apache server to have access to the ban list and manually parse through the logs to get the time. Ok, I just read all the previous and see it is in your code and it sounds like you are doing a day. This banning might ban someone, while it's active, who makes a mistake, but I think that's way better than stopping everyone logging in.
... and anyone who gets on by mistake, can always contact me to get off the ban list very quickly.
There's only been about 700 banned IPs, but I did completely block a bunch of large subnets before hand that were all bots.
Most of the previous banning has been either IP subnets that had very large numbers of bots, or simply disabling logins for a short while until they got bored having no effect on anything.
This one has sorta gone on all day, so this solution is the best in this case, in my opinion.
Lastly, most people with more than a few miners, have a different place/places for their miners.
Personally in my code, I allow 3 attempts, then lock for 5 minutes then 15 on the next, then 60 on the next and a day one the next. I have detection for all kinds of hacker things (injection, arrays, etc) and if the server detects those, then the ip is blocked for a day. As with yours, I do most in my code although my servers also have a firewall that blocks on ssh attempts, etc. It seems that it would be good if you had something in place all the time rather than manually turning on and off your systems when threats are detected. I suspect that even you need to sleep once in a while.
December 26, 2017, 03:14:58 AM
Is there a way to create a white list of Ip addresses of people that are actually mining to the pool, and can make the assumption that they are using the same IP address for their web login since it would be on the same connection. If the IP address exists in that DB, then you can have multiple wrong password attempts, if you are not on that list you have 0 tolerance.
Or to have even more fun, when there is a bad set of credentials sent, it sends the user to a completely different server just to make the bots stop attempting to login. Or just allow the bots on the IP addresses that you have collected log in ( By redirecting to another site ) and so they will stop hopefully. They are probably coded to just hammer the site, but not coded on what to do after a "successful" login to the fake site.
Firstly, the banning is working fine, and this is the first time I've enabled this extra blocking, that already existed in the code when I first wrote it all, and it's working fine also.Or to have even more fun, when there is a bad set of credentials sent, it sends the user to a completely different server just to make the bots stop attempting to login. Or just allow the bots on the IP addresses that you have collected log in ( By redirecting to another site ) and so they will stop hopefully. They are probably coded to just hammer the site, but not coded on what to do after a "successful" login to the fake site.
This banning might ban someone, while it's active, who makes a mistake, but I think that's way better than stopping everyone logging in.
... and anyone who gets on by mistake, can always contact me to get off the ban list very quickly.
There's only been about 700 banned IPs, but I did completely block a bunch of large subnets before hand that were all bots.
Most of the previous banning has been either IP subnets that had very large numbers of bots, or simply disabling logins for a short while until they got bored having no effect on anything.
This one has sorta gone on all day, so this solution is the best in this case, in my opinion.
Lastly, most people with more than a few miners, have a different place/places for their miners.
December 26, 2017, 02:56:05 AM
Is there a way to create a white list of Ip addresses of people that are actually mining to the pool, and can make the assumption that they are using the same IP address for their web login since it would be on the same connection. If the IP address exists in that DB, then you can have multiple wrong password attempts, if you are not on that list you have 0 tolerance.
Or to have even more fun, when there is a bad set of credentials sent, it sends the user to a completely different server just to make the bots stop attempting to login. Or just allow the bots on the IP addresses that you have collected log in ( By redirecting to another site ) and so they will stop hopefully. They are probably coded to just hammer the site, but not coded on what to do after a "successful" login to the fake site.
Or to have even more fun, when there is a bad set of credentials sent, it sends the user to a completely different server just to make the bots stop attempting to login. Or just allow the bots on the IP addresses that you have collected log in ( By redirecting to another site ) and so they will stop hopefully. They are probably coded to just hammer the site, but not coded on what to do after a "successful" login to the fake site.
December 26, 2017, 02:37:57 AM
happy holidays everyone! 
@kano
what does luck 5, luck 10, luck 25, luck 50 means?
If you mean the "Luck%" column in the "Block Statistics" table:@kano
what does luck 5, luck 10, luck 25, luck 50 means?
It's just the "Luck%" over the Last "than many" Blocks.
Of course the 5,10,25 and probably also the 50 numbers are pretty much meaningless in the realm of useful statistical samples (and I have considered removing them in the past) but they are still there none-the-less
December 26, 2017, 02:15:09 AM
My estimate for next BTC mining difficulty: drop between -1% to 0% around 2018/01/01 14:00
1 869 539 787 755 -0.19% . 18/01/01 14:33
Any other estimates ?
1 869 539 787 755 -0.19% . 18/01/01 14:33
Any other estimates ?
December 26, 2017, 02:08:44 AM
happy holidays everyone!
@kano
what does luck 5, luck 10, luck 25, luck 50 means?
@kano
what does luck 5, luck 10, luck 25, luck 50 means?
Jump to: