[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[Sebz4n]

How to reduce idle time!
Hey guys, I see that a lot of people are having issues with connection time outs and much idle time.
I found a quite simple "solution" to this, which you may not have thought of.

I have two GPU's that I mine with, using GUIMiner, now, I had the same issues you do, connection problems,
time outs, idle etc...

So I started running 4 miners on my two cards instead of one, currently Slush has two pool links going on:
mining.bitcoin.cz
api.bitcoin.cz

So set up your GPUs so they mine to BOTH addresses, if one drops out, it will transfer the Mhash/s to the one
that is still working, and vice versa. This will at least reduce idle time a great bit, and I haven't seen both links
time out at the same time yet

Peace!

[1714295181]

1714295181

[OCNewB]

I see the IP list in my account option now but even with my IP in there, i still can't get my miners to connect to Slush.

[OggerMC]

thanks for that share. Going to try it once i get even one address to work at all.

Really strange. Ive added my Current IP AND my DNS and i still cant connect.

[nomnomnom]

I see the IP list in my account option now but even with my IP in there, i still can't get my miners to connect to Slush.

did you use api.bitcoin.cz or mining2.bitcoin.cz?
slush posted a page back that we should point the miners there.

[FooDSt4mP]

Slush, I have a new dynamic IP every 24 hours thanks to how my ISP works.

I have no idea how to tell your whitelister to accept  *.myisp.domain ranges for possible IPs.

So far it seems it only accepts single IPs or a DNS string that resolves to a single IP.

Both dns name and IP change 24h, and I would miss half a day of mining if you restrict worker useage like this without full domain ranges.



--

I have not received an email about the whitelist / whitelist format yet.

--

Someone should seriously figure out the origins of the ongoing DDOS attacks (they've been going on since > 5 week snow) and sue the living crap out of these ***holes.

dyndns.org: problem solved

If Slush is smart, he doesn't want to allow *.yourisp because then everyone on your isp can dos him... that's defeats the purpose of a whitelist.

[evlew]

My workers are currently connected to mining.bitcoin.cz.
I've added my ip address to the white list in my account settings.
am I good to go or do I need to switch servers as well?

If i do, that sucks, because I am stuck at work.

[slush]

Hi guys, I just updated website to allow registering IP addresses and hostnames, but this list isn't alive yet - I'm just collecting your IPs. So please fill in what IP you're using.

You can fill any domain name, even dynamic one. It's why there is 'resolved IP' column; pool will refresh IP time to time (not sure how often, depends on number of IPs), so IP list should be up to date.

For those without static IP (and even without dynamic dns), I'll introduce new API URL (which will be using API token which is already presented), which will detect IP of remote host and automatically update firewall settings. So short script on your side detecting IP change or even support in miners (GUI miner for windows?) would easily solve the problem.

Stay tuned, I'm going to knock up that firewall part, full whitelisting will be enabled soon!

[OCNewB]

I see the IP list in my account option now but even with my IP in there, i still can't get my miners to connect to Slush.

did you use api.bitcoin.cz or mining2.bitcoin.cz?
slush posted a page back that we should point the miners there.

I used both api.bitcoin.nz and the other one but none worked. I'm not sure if i got my IP correct or not tho. I googled IP address and the website "whatismyIPaddress" showed me mine. Anyway not sure why i can't get my miners to connect to Slush still.

[OCNewB]

Hi guys, I just updated website to allow registering IP addresses and hostnames, but this list isn't alive yet - I'm just collecting your IPs. So please fill in what IP you're using.

You can fill any domain name, even dynamic one. It's why there is 'resolved IP' column; pool will refresh IP time to time (not sure how often, depends on number of IPs), so IP list should be up to date.

For those without static IP (and even without dynamic dns), I'll introduce new API URL (which will be using API token which is already presented), which will detect IP of remote host and automatically update firewall settings. So short script on your side detecting IP change or even support in miners (GUI miner for windows?) would easily solve the problem.

Stay tuned, I'm going to knock up that firewall part, full whitelisting will be enabled soon!

Thanks for the update Slush, i guess i'll need to wait a little while more then.

[Justsomeforumuser]

For those without static IP (and even without dynamic dns), I'll introduce new API URL (which will be using API token which is already presented), which will detect IP of remote host and automatically update firewall settings. So short script on your side detecting IP change or even support in miners (GUI miner for windows?) would easily solve the problem.

Stay tuned, I'm going to knock up that firewall part, full whitelisting will be enabled soon!

Windows 7 x64 and guiminer here.

Maybe simply whitelisting the IP if it provides the correct user / pass reply will already take care of the whole issue? 

I would have thought that was the whole point of using login credentials in the first place.

[Transisto]

I have my IP white-listed but none can connect.

[zale]

I see the IP list in my account option now but even with my IP in there, i still can't get my miners to connect to Slush.

did you use api.bitcoin.cz or mining2.bitcoin.cz?
slush posted a page back that we should point the miners there.

I used both api.bitcoin.nz and the other one but none worked. I'm not sure if i got my IP correct or not tho. I googled IP address and the website "whatismyIPaddress" showed me mine. Anyway not sure why i can't get my miners to connect to Slush still.

Some for me. I got a connection once for about 3 seconds and then got disconnected again.

[slush]

I used both api.bitcoin.nz and the other one but none worked. I'm not sure if i got my IP correct or not tho. I googled IP address and the website "whatismyIPaddress" showed me mine. Anyway not sure why i can't get my miners to connect to Slush still.

Well, it's .cz, not .nz

Btw, again, ips from profile pages are not yet active.

[OggerMC]

Its finally working for me again, thanks a lot!
In the time meantime i was OCing my card to its Limits!
Awesome to get 396 Mhash/s out of a 5850 (not water cooled)

[OCNewB]

Yep it's working now  . I'm glad i could mine @ Slush pool again.

[Jarredm]

How to reduce idle time!
Hey guys, I see that a lot of people are having issues with connection time outs and much idle time.
I found a quite simple "solution" to this, which you may not have thought of.

I have two GPU's that I mine with, using GUIMiner, now, I had the same issues you do, connection problems,
time outs, idle etc...

So I started running 4 miners on my two cards instead of one, currently Slush has two pool links going on:
mining.bitcoin.cz
api.bitcoin.cz

So set up your GPUs so they mine to BOTH addresses, if one drops out, it will transfer the Mhash/s to the one
that is still working, and vice versa. This will at least reduce idle time a great bit, and I haven't seen both links
time out at the same time yet

Peace!

So with this config, do you make 2 workers for each of your cores?  Although I don't know what the problem with multiple workers logging into the same account I know that it is always said to use one worker for each worker process you run.  With Sebz4n's strategy you will often have two workers connecting that are using the same processing core.

What is the recommended config here?  Slush maybe you can provide some guidance.  I imagine that this may not be necessary forever, but just until the connection issues are corrected is that safe to assume?

[kitsura]

How to reduce idle time!
Hey guys, I see that a lot of people are having issues with connection time outs and much idle time.
I found a quite simple "solution" to this, which you may not have thought of.

I have two GPU's that I mine with, using GUIMiner, now, I had the same issues you do, connection problems,
time outs, idle etc...

So I started running 4 miners on my two cards instead of one, currently Slush has two pool links going on:
mining.bitcoin.cz
api.bitcoin.cz

So set up your GPUs so they mine to BOTH addresses, if one drops out, it will transfer the Mhash/s to the one
that is still working, and vice versa. This will at least reduce idle time a great bit, and I haven't seen both links
time out at the same time yet

Peace!

Do a ping on both hostnames and you will find that it connects to the same IP. Pointing so many miners to them is not the solution! What you are effectively doing is DoSing the server since you are increasing its load. I advise you to have patience since the DDoS and increased load is currently overloading the servers so that's why your requests are getting timed out.

[Jarredm]

How to reduce idle time!
Hey guys, I see that a lot of people are having issues with connection time outs and much idle time.
I found a quite simple "solution" to this, which you may not have thought of.

I have two GPU's that I mine with, using GUIMiner, now, I had the same issues you do, connection problems,
time outs, idle etc...

So I started running 4 miners on my two cards instead of one, currently Slush has two pool links going on:
mining.bitcoin.cz
api.bitcoin.cz

So set up your GPUs so they mine to BOTH addresses, if one drops out, it will transfer the Mhash/s to the one
that is still working, and vice versa. This will at least reduce idle time a great bit, and I haven't seen both links
time out at the same time yet

Peace!

Do a ping on both hostnames and you will find that it connects to the same IP. Pointing so many miners to them is not the solution! What you are effectively doing is DoSing the server since you are increasing its load. I advise you to have patience since the DDoS and increased load is currently overloading the servers so that's why your requests are getting timed out.

While you are right that it is increasing overall getwork request load, we don't really know for sure that it is pointing to the same location.  If there were no difference between them then slush would not have needed to add a new host name.  The resolved IP is most likely a load balancer which could be routing traffic selectively based on what the requested host name is in the HTTP GET request.  This is the same concept that allows you to host multiple websites with the same server & IP address.  We need slush to weigh in on this.

[qed]

API are reporting wrong miner status. flagged as "active" even if it is not for a long period of time.

[slush]

While you are right that it is increasing overall getwork request load, we don't really know for sure that it is pointing to the same location.  If there were no difference between them then slush would not have needed to add a new host name.  The resolved IP is most likely a load balancer which could be routing traffic selectively based on what the requested host name is in the HTTP GET request.  This is the same concept that allows you to host multiple websites with the same server & IP address.  We need slush to weigh in on this.

Actually mining.bitcoin.cz and api.bitcoin.cz is the same machine. But firstly we need to split traffic website/mining between two domains, then I can move one domain to another machine. I hope it will be possible tomorrow.