Okay. Try this other thing. Download slush's stratum proxy - http://mining.bitcoin.cz/mining-proxy-howtoOpen a command line cd to the download folder run 'mining_proxy.exe -o us.eclipsemc.com -p 333 -gp 8332' You may have to hit 'Switch Server' on your config page. Let me know how that works. |
|
|
|
|
So you got stratum_proxy running and pointed at your pool. Your blades are pointed at the machine running the proxy? And the gateway is set right on the blade?
|
|
|
|
|
I can't see it being an issue. Try the instructions from the other thread and see if it works. Should only take a minute to test.
|
|
|
|
|
Did you try Slush's mining_proxy?
|
|
|
|
|
See previous post - fairly straightforward for Slush's stratum proxy. Runs standalone in a command line.
|
|
|
|
Download slush's stratum proxy - http://mining.bitcoin.cz/mining-proxy-howtoOpen a command line cd to the download folder run 'mining_proxy.exe -o us.eclipsemc.com -p 333 -gp 8332' You may have to hit 'Switch Server' on your config page. Let me know how that works. |
|
|
|
|
Try fetching the current version of BFG
Scratch the -S and --icarus anything, include -S erupter:all --http-port 8332
|
|
|
|
|
If you were on cgminer and slush proxy I'd have you going already. Darn this learning new software stuff...
|
|
|
|
|
Newer versions of BFG probably use something different than --icarus for Block Erupters.
|
|
|
|
|
How old is your current version? That could be the issue - if it predates stratum proxy implementation, the unrecognized command might be throwing it for a loop.
|
|
|
|
|
What happens if you run it straight from a command line?
'cd' to the folder where bfgminer.exe is, then type in the same as your target line in that shortcut link.
|
|
|
|
|
The blade's default gateway and primary DNS are currently set to 192.168.0.1?
You put --http-port 8332 in the shortcut target line and restarted BFG using that shortcut?
|
|
|
|
|
Yes, you'll want the gateway and DNS set to your 0.x subnet
|
|
|
|
|
According to 7queue in an earlier reply, you need to tuck a "--http-port 8332" in there somewhere. Put that in the line, restart BFG using that shortcut, and point your blades to server 192.168.0.3, port 8332 and see if they light up.
|
|
|
|
|
Is BFG already pointed at your eclipsemc pool?
What's the contents of the shortcut? Like when you right-click-> properties, what's the "target" line read?
|
|
|
|
|
That's something I can't help you with, never used BFG. If you search the forums for BFG Stratum Proxy, you'll probably turn up some worthwhile results.
|
|
|
|
|
Using the pool's getwork will probably be okay as a test of connectivity and functionality, but for high-hash devices getwork tends to drop efficiency because of network latency going through the internet. If you see hashrate or efficiency are pretty low, you'll definitely want to set up a proxy.
Yes, the server and ports should both be entered twice, with a comma inbetween.
|
|
|
|
|
If your pool has a getwork node available, you can put the pool's address in the server address and the getwork listen port in the Ports box. You need two sets of info, blades won't work without a fallback listed but both entries can be the same.
If your preferred pool does not have a getwork node, or you want it to actually work efficiently, download a stratum proxy - either Slush's mining_proxy, or BFGMiner.
I only know how to configure Slush's mining_proxy, which is pretty straightforward.
In a command prompt, navigate to the folder where the .exe was dowloaded to. "cd" is the change directory command.
Your command line will look like "mining_proxy.exe -o poolserver -p stratumport -gp getworkport"
I think the -gp isn't really required, not sure what it defaults to but it never hurts to be explicit. This should be the same number as the "Ports" field in the config page. The -o and -p are the server and port for your pool.
In the blade config, set the Server address to your computer's IP (192.168.0.3, if I remember right) and populate the user:pass field with your pool's worker credentials.
|
|
|
|
Okay so we know that works. You probably don't want the blade tethered to your laptop forever. Change the settings on the blade - IP: 192.168.0.254 Mask: 255.255.255.0 Gateway: 192.168.0.1 Hit Update/Restart Change the IP on your computer's LAN connection to 192.168.0.whatever Ping 192.168.0.254 Navigate to http://192.168.0.254:8000/MainIf all that works, plug the blade back into your router and see if you can still access the config page. |
|
|
|
|
Show Posts
