[Guide] Dogie's Comprehensive ASICMiner Cube Setup [HD]

[JLebowskiTheDude]

well, ive gotten the cube up, all good chips, my issue i think is connecting to the computer running the proxy.

the proxy is receiving work orders i have the pool address as the computer running the proxy, and i have an account on slush's pool so i put my username and password in as directed.  however the cube remains 'inactive'

i still cant upload photos for some reason

Even though the Stratum Proxy uses Slush's by default I still recommend configuring the CLI manually so you have more granular control.  It also helps you learn the CLI syntax, which should you need to have a backup pool or switch pools, is helpful.

So if you're using Windows the syntax would be:

Code:

mining_proxy.exe -o stratum.bitcoin.cz -p 3333 -gp YourComputersStratumProxyPort

Where YourComputersStratumProxyPort is an opened port on the computer you're running the Stratum Proxy on.  Make sure you have allowed communication on that port with whatever firewall you're employing.

For the Cube configuration, the correct syntax should be

Code:

SlushsPoolUsername.YourWorker:YourPassword, SlushsPoolUsername.YourWorker:YourPassword

Note the dot instead of the underscore.

Otherwise post your exact Cube configuration details for more help.

[1715188988]

1715188988

[1715188988]

1715188988

[1715188988]

1715188988

[JLebowskiTheDude]

Full information can be found on theAndroid Open Source Project - Issue Tracker: https://code.google.com/p/android/issues/detail?id=11236 "DHCP client ignores lease time".

One thing that may help is to make sure the Cube(s) and any proxy are on addresses outside the DHCP pool so there will not be any collisions.

Thanks for the update on this. 

It didn't affect me specifically because by default I did set the Cubes' IP addresses outside the DHCP (just an old habit), but I'm sure this will help others.

[allengrad]

i was having my issue with imgur, fixed now https://i.imgur.com/9ca58Dl.png  https://i.imgur.com/SgEbPaD.png
https://i.imgur.com/lIAjJGc.png

[JLebowskiTheDude]

i was having my issue with imgur, fixed now

Cube configuration is incorrect.  The third octet of your IP addresses is using .1 when your network appears to use .0.

First change the IP of the Cube from 192.168.1.254 to something in the .0 range that is outside your DHCP range.  Make sure it doesn't conflict with any other devices on your network already on 192.168.0.X.  Something like 192.168.0.50 should probably work.  Reboot the Cube first after IP change.  Then access it on the whatever the new IP address is using port 8000.  So in this example 192.68.0.50:8000.

Also you have a typo in the second value of Pool address.  The + sign.

So the correct values in the configuration would be -

IP: 192.168.0.50 (or whatever value you decide above)
Mask: 255.255.255.0
Gateway: 192.168.0.1
WEB Port: 8000
Primary DNS: 192.168.0.1
Secondary DNS: 8.8.8.8
Pool Ports: 8330,8330
Pool Addresses: 192.168.0.17,192.168.0.17
Miners user:pass: Current settings you have are fine

[DanZaph]

The first thing that jumps out is the "+" in the second Pool address, it should not be there.
The gateway is 0.0.0.0 which I understand is OK but I personally put in the address of the router.
The proxy (pool) address is 192.169.0.17
The Cube address is 192.168.1.254
The Mask is 255.255.255.0
This means that the Cure and the proxy are on different networks (logically) and will not be able to communicate.
Question:
What is the IP address of your router, with that information I can provide instructions for setting up the Cube..
Need to do:
Get both the Cube and proxy on the same network but need the router address with no address conflicts.

Note: JLebowskiTheDude is assuming that your router is on the 192.168.0.x network but that may be incorrect, your router may be on the 192.168.1.x network.

[allengrad]

i was having my issue with imgur, fixed now https://i.imgur.com/9ca58Dl.png

Cube configuration is incorrect.  The third octet of your IP addresses is using .1 when your network appears to use .0.

First change the IP of the Cube from 192.168.1.254 to something in the .0 range that is outside your DHCP range.  Make sure it doesn't conflict with any other devices on your network already on 192.168.0.X.  Something like 192.168.0.50 should probably work.  Reboot the Cube first after IP change.  Then access it on the whatever the new IP address is using port 8000.  So in this example 192.68.0.50:8000.

Also you have a typo in the second value of Pool address.  The + sign.

So the correct values in the configuration would be -

IP: 192.168.0.50 (or whatever value you decide above)
Mask: 255.255.255.0
Gateway: 192.168.0.1
WEB Port: 8000
Primary DNS: 192.168.0.1
Secondary DNS: 8.8.8.8
Pool Ports: 8330,8330
Pool Addresses: 192.168.0.17,192.168.0.17
Miners user:pass: Current settings you have are fine

https://i.imgur.com/8LPS8fI.png

[JLebowskiTheDude]

Note: JLebowskiTheDude is assuming that your router is on the 192.168.0.x network but that may be incorrect, your router may be on the 192.168.1.x network.

ipconfig screenshot shows 192.168.0.1 as default gateway and DHCP server.

[JLebowskiTheDude]

First, you need to wait longer than 3 seconds after the Cube reboots.  

Second, you may need to restart the Stratum Proxy.

You didn't post any info about the settings you're using for your mining_proxy.exe.

Lastly, ensure 8330 is open on any firewall running on 192.168.0.17.

[DanZaph]

Note: JLebowskiTheDude is assuming that your router is on the 192.168.0.x network but that may be incorrect, your router may be on the 192.168.1.x network.

ipconfig screenshot shows 192.168.0.1 as default gateway and DHCP server.

I was wondering how he was communication to the Cube when the Cube was on a 192.168.0.x network.
Hopefully allengrad is good to go now.

[JLebowskiTheDude]

I was wondering how he was communication to the Cube when the Cube was on a 192.168.0.x network.
Hopefully allengrad is good to go now.

Well it could be set-up so that where the Stratum Proxy was running was on a different part of the network than the Cube was on.  But it's not an ideal configuration for a beginner setting it up for the first time.  

What you said it true.  Get everything on the same internal network first.

Crawl before running as they say.  

[allengrad]

that was after an additional restart. the proxy is running on port 3333 and 8332, do i adjust that in the cubes pool port?

[JLebowskiTheDude]

that was after an additional restart. the proxy is running on port 3333 and 8332, do i adjust that in the cubes pool port?

It can take more than a few seconds after any reboot to start hashing.

That should be server port 3333 and 192.168.0.17 port 8332, yes?  One Slush controls the choice of, the other you do.

Yes.  You need to change that in the Pool Ports section.

So new settings should be

IP: 192.168.0.50
Mask: 255.255.255.0
Gateway: 192.168.0.1
WEB Port: 8000
Primary DNS: 192.168.0.1
Secondary DNS: 8.8.8.8
Pool Ports: 8332,8332
Pool Addresses: 192.168.0.17,192.168.0.17
Miners user:pass: Current settings you have are fine but ensure your worker name and password are correct by logging into your Slush account and double checking, since we are being thorough now.

Also make sure 8332 now (not 8330) is opened in any firewall running on 192.168.0.17.

Restart the Cube and mining_proxy.exe after any changes just to be sure.

[allengrad]

For testing purposes I disabled the firewall completely. i also forwarded ports on my router, though i'm pretty sure i screwed that up.
cube has been running for about 10 minutes i have sat with and refreshed every 10 seconds and after 2 minutes and 5 seconds it goes back to 0.

https://i.imgur.com/ArfNfwn.png

https://i.imgur.com/29mnUVR.png

https://i.imgur.com/W3NDUKv.png

https://i.imgur.com/83bHCFR.png

[JLebowskiTheDude]

For testing purposes I disabled the firewall completely. i also forwarded ports on my router, though i'm pretty sure i screwed that up.

That may very well be the problem.  You don't need to forward any ports on your router.  I have no idea why you thought that had to be done.

You need to open any firewall application running on 192.168.0.17 (aka GameRig) to allow communication on port 8332.  Like, for example, if you were running Windows Firewall, Comodo, etc.

Remove or disable all those forwarding rules you've created on your router.  Reboot your router.

Then reboot the Cube and restart mining_proxy.exe.

[allengrad]

removed all the port forwarding, a friend told me that i needed to do it, those changes are gone, rebooted router, cube and proxy, letting run will update in 10. thanks again for the help.

[JLebowskiTheDude]

removed all the port forwarding, a friend told me that i needed to do it, those changes are gone, rebooted router, cube and proxy, letting run will update in 10. thanks again for the help.

You're welcome!  You definitely started from a very weird combination of settings. 

Hoping it's all sorted out now.

[allengrad]

well it hasn't been 10 cube's started before time goes back to 0 after 2m13s

still inactive.

i have restarted the proxy while leaving the cube up, and vice versa. have also restarted both simultaneously. proxy is receiving jobs, i think the cube is having an issue connecting to the computer running the proxy now.


including cube config below. i'm pretty sure i have all the info correct

https://i.imgur.com/2fBIYAC.png
https://i.imgur.com/JpmKS9I.png
https://i.imgur.com/2S3bzEP.png

[divinesnail01]

well it hasn't been 10 cube's started before time goes back to 0 after 2m13s

still inactive.

i have restarted the proxy while leaving the cube up, and vice versa. have also restarted both simultaneously. proxy is receiving jobs, i think the cube is having an issue connecting to the computer running the proxy now.


including cube config below. i'm pretty sure i have all the info correct

https://i.imgur.com/2fBIYAC.png
https://i.imgur.com/JpmKS9I.png
https://i.imgur.com/2S3bzEP.png

It looks like you have the cube pointing to .17 for the pool, but your PC is at .2.  That's not going to work.

The pool on the cube should be set to the same as the IPV4 address on the PC running the proxy software.

[JLebowskiTheDude]

including cube config below. i'm pretty sure i have all the info correct

Yeah you don't.  Mostly not your fault this time though!  You were leased a new IP on the router reboot you did after removing the Forwarding Rules.

What divinesnail01 said below is mostly correctly... with a big caveat since divinesnail01 just arrived in the middle of this.

It looks like you have the cube pointing to .17 for the pool, but your PC is at .2.  That's not going to work.

The pool on the cube should be set to the same as the IPV4 address on the PC running the proxy software.

However, his PC running the Stratum Proxy was .0.17 just a few moments ago.



I'd suggest setting up a static IP for GameRig.  

You don't want to have to change the cube configuration if/when your router decides to lease GameRig a different internal IP address.

Whatever address you decide on GameRig being, go back and change the Cube configuration Pool Addresses field again to match.

[allengrad]

it appears as though my computer's ip changed. changed settings, all good now. (set pc on static ip to prevent issues in future.)

thanks for all the help =D

Cheers