MultiMiner: Any Miner, Any Where, on Any Device (Free, Open Source, Cross Platform)

[Miasma]

Seasons Greetings Nate, I enabled Stratum Proxy under perks and have been trying to get it to tell my AntMiner S3s where to mine. I set Permitted IPs as 127.0.0.1,192.168.1.0/24. I SSHed into each miner and set /etc/config to have option api_allow 'W:127.0.0.1,W:192.168.1.0/24', and in /etc/init.d I deleted --api-network and replaced it with --api-allow $_aa. I rebooted each S3 after saving changes. I don't think I understand how to "point my S3 at the stratum proxy." The PC running MuM 3.8.1 is 192.168.1.253 and an S3 is 192.168.1.5.
Am I supposed to delete the entries in the S3 under Miner Configuration and add 192.168.1.253:3333 for Pool 1

I tried stratum+tcp://192.168.1.253:3333 for my Pool 1 URL but that's not working either. I see a line in MuM Stratum Proxy #1 BitCoin but nothing is happening.

I'm a bit confused as to what you are trying to do. I think you are combining / confusing two separate features found in MultiMiner.

The first is support for monitoring and managing Network Devices. This has nothing to do with the Stratum Proxy feature. This feature means that, if you take the proper steps to enable the RPC API on your Network Device controller, MultiMiner will automatically display the ASIC under the Network section in the main window.

The Stratum Proxy feature allows you to point any other miner, be it a desktop miner or Network Device, at the IP address of MultiMiner and the port specified in the Stratum Proxy settings. BFGMiner will proxy the work from the miner to the pool configured within MultiMiner. Note that you must click the Start button to start the Stratum Proxy (and other miners). This will require you to adjust firewall settings on the PC MultiMiner is running on.

Which is it you are trying to do and having trouble with?

This one: "The Stratum Proxy feature allows you to point any other miner, be it a desktop miner or Network Device, at the IP address of MultiMiner and the port specified in the Stratum Proxy settings. BFGMiner will proxy the work from the miner to the pool configured within MultiMiner. Note that you must click the Start button to start the Stratum Proxy (and other miners). This will require you to adjust firewall settings on the PC MultiMiner is running on."
I scanned hardware and clicked start and closed the program and reopened it.

[Axiste]

make sure the stratum proxy is turned on in the settings, then scan hardware (shouldnt need to scan in newer versions) then righ clock the proxy device, set the coin it is to mine, then click start.
If you close MultiMiner, and reopen it, then you need to click start again.

then point all your miners to the MultiMiner box IP address and the port for stratum or http port of your proxy. Ensure any firewalls have the port set to open (eg windows firewall).

[Miasma]

make sure the stratum proxy is turned on in the settings, then scan hardware (shouldnt need to scan in newer versions) then righ clock the proxy device, set the coin it is to mine, then click start.
If you close MultiMiner, and reopen it, then you need to click start again.

then point all your miners to the MultiMiner box IP address and the port for stratum or http port of your proxy. Ensure any firewalls have the port set to open (eg windows firewall).

Thanks, but it still does not work. I created a new Inbound Rule in Win7 firewall called Stratum Proxy to open 3333 to all. I have enabled Stratum port 3333 under Advanced miner settings/Proxy settings. I've scanned hardware and see all my S3s in MuM under Network. I saw somewhere that if they're mining via the stratum proxy that they stop appearing under Network. In the section called Proxy I checked the box Stratum Proxy #1 that says it's mining BitCoin.

MuM is set to "Begin mining when the app starts" and I've also tried clicking the Restart below the Stop button.

How do I point an S3
I entered stratum+tcp://192.168.1.253:3333 under Miner Configuration Pool 1. I left worker and password blank. I also tried 192.168.1.253:3333.
This PC is running MuM 3.8.1 with IP address 192.168.1.253
TIA

[Axiste]

Each one needs a unique worker name, and a random password.

Also what pool is the proxy set to mine? if its mining to a local wallet, the stratum proxy wont work.

Edit: To be more precise, each S3 needs a unique worker name and just put x as the password. You do not need to set up usernames anywhere, just make one up when you enter it into the S3.

[Miasma]

In the MuM Configure Strategies there are two lines that both say "Don't mine coins less profitable than." The first line is followed by a pulldown menu to select a coin. The second line is followed by an empty box. What goes in the box
I tried a number, e.g. 105, to mean a coin must be 5% more profitable than BitCoin to be mined. But that does nothing.
There is no explanation offered if one clicks on the Help question mark: https://github.com/nwoolls/MultiMiner/wiki/Auto-Mining-Strategies

[Miasma]

Since I started mining SHA through the Stratum Proxy my HW errors have skyrocketed, up over 100x. Anyone know why

[nwoolls]

In the MuM Configure Strategies there are two lines that both say "Don't mine coins less profitable than." The first line is followed by a pulldown menu to select a coin. The second line is followed by an empty box. What goes in the box

Profitability is one of the columns displayed in the main screen of the application and is returned by the Coin APIs (either CoinChoose, CoinWarz or WhatMine). Setting a value in that box means that MultiMiner will not automatically switch to coins that are less profitable than that value when the Auto Mining Strategies are enabled.

[nwoolls]

Since I started mining SHA through the Stratum Proxy my HW errors have skyrocketed, up over 100x. Anyone know why

My first question would be - if you have time - how did you get the Stratum Proxy feature working after your previous failed attempts? That information may help others who run into the same issue.

Regarding hardware errors, what does the hashrate look like on the pool side (checking your pool stats)? If the Stratum Proxy is indeed introducing additional HW errors please try reproducing it with only BFGMiner (you can see the arguments passed by checking the Process Log button on the left), e.g.:

Code:

--load-balance --scan noauto --http-port 8332 --stratum-port 3333 --o "stratum+tcp://the.real.pool.com:3333" -u username -p password

If the HW errors persist with only BFGMiner, please report the issue and details in the BFGMiner thread.

[Miasma]

As Axiste explained, I added a user name and password to the S3s Miner Configuration Pool 1 table:
stratum+tcp://192.168.1.253:3333
S3_13
pw

[nwoolls]

As Axiste explained, I added a user name and password to the S3s Miner Configuration Pool 1 table:
stratum+tcp://192.168.1.253:3333
S3_13
pw

Awesome - thank you! 

[nwoolls]

Happy holidays!

MultiMiner version 3.8.2 is now available for download with the following changes:

• Added the ability to Start and Stop mining on selected Network Devices - includes MobileMiner support for Remote Commands (multi-select supported, no SSH access required)
• Additional handling for Blockchain.info API specific errors
• Fixed an issue where the main screen stats would stop updating
• Fixed the Scan Hardware action hiding virtual Proxy Devices
• Fixed inability to check / enable newly added Proxy Devices
• Fixed a rare crash writing to log files

If you have any feature requests or issues please log them here:

http://issues.multiminerapp.com

And for help on using the app, see:

http://help.multiminerapp.com

As always, source code is available at:

http://source.multiminerapp.com

Finally, to learn how to contribute, visit:

http://contribute.multiminerapp.com

Happy mining!  

[AJinNYC]

I'm having a problem getting MultiMiner to detect my S3+. Not sure if it might be an issue with the WAMP stack I have on my computer (on localhost/127.0.0.1)?

I SSH'd into the S3 and modified what needed to be modified, but still not coming up.

'W:127.0.0.1,W:10.0.0.1/24'

and --api-network was changed to --api-allow $_aa

[nwoolls]

I'm having a problem getting MultiMiner to detect my S3+. Not sure if it might be an issue with the WAMP stack I have on my computer (on localhost/127.0.0.1)?

I SSH'd into the S3 and modified what needed to be modified, but still not coming up.

'W:127.0.0.1,W:10.0.0.1/24'

and --api-network was changed to --api-allow $_aa

What is the IP of the MultiMiner PC and of the S3?

You can try adding the IP to NetworkDevicesConfiguration.xml (in %appdata%\MultiMiner) while MultiMiner is closed if the automatic scan isn't picking it up.

[AJinNYC]

I'm having a problem getting MultiMiner to detect my S3+. Not sure if it might be an issue with the WAMP stack I have on my computer (on localhost/127.0.0.1)?

I SSH'd into the S3 and modified what needed to be modified, but still not coming up.

'W:127.0.0.1,W:10.0.0.1/24'

and --api-network was changed to --api-allow $_aa

What is the IP of the MultiMiner PC and of the S3?

You can try adding the IP to NetworkDevicesConfiguration.xml (in %appdata%\MultiMiner) while MultiMiner is closed if the automatic scan isn't picking it up.

The MM Comp is 10.0.0.3 and the S3 is 10.0.0.99.

[nwoolls]

I'm having a problem getting MultiMiner to detect my S3+. Not sure if it might be an issue with the WAMP stack I have on my computer (on localhost/127.0.0.1)?

I SSH'd into the S3 and modified what needed to be modified, but still not coming up.

'W:127.0.0.1,W:10.0.0.1/24'

and --api-network was changed to --api-allow $_aa

What is the IP of the MultiMiner PC and of the S3?

You can try adding the IP to NetworkDevicesConfiguration.xml (in %appdata%\MultiMiner) while MultiMiner is closed if the automatic scan isn't picking it up.

The MM Comp is 10.0.0.3 and the S3 is 10.0.0.99.

Should work fine - try adding it manually to the XML file if the scan isn't working. If it still isn't showing then the RPC API on the ASIC isn't responding. Make sure you restarted mining on the S3 after all the config changes.

[z0n0]

Nate, will there ever be CPU supported mining with multiminer?

[nwoolls]

Nate, will there ever be CPU supported mining with multiminer?

MultiMiner supports CPU mining and has for some time (seen in this screenshot). But you need to compile a version of BFGMiner with CPU support. Nobody distributes those currently as they are used by malware authors and lend to antivirus apps flagging BFGMiner and the likes as viruses.

There are instructions for compiling BFGMiner for Windows (with CPU mining support) here:

https://github.com/luke-jr/bfgminer/blob/bfgminer/windows-build.txt

Drop it into Miners\BFGMiner afterward and Scan Hardware should pick up your CPUs.

You can read more about it on the wiki:

https://github.com/nwoolls/MultiMiner/wiki/CPU-Mining#cpu-mining

[z0n0]

Nate, will there ever be CPU supported mining with multiminer?

MultiMiner supports CPU mining and has for some time (seen in this screenshot). But you need to compile a version of BFGMiner with CPU support. Nobody distributes those currently as they are used by malware authors and lend to antivirus apps flagging BFGMiner and the likes as viruses.

There are instructions for compiling BFGMiner for Windows (with CPU mining support) here:

https://github.com/luke-jr/bfgminer/blob/bfgminer/windows-build.txt

Drop it into Miners\BFGMiner afterward and Scan Hardware should pick up your CPUs.

You can read more about it on the wiki:

https://github.com/nwoolls/MultiMiner/wiki/CPU-Mining#cpu-mining

Didn't know about that thanks for quick answer
cheers

[nwoolls]

Happy holidays!

MultiMiner version 3.8.3 is now available for download with the following changes:

• Rewritten Network Device scan code supports a wider variety of LAN configurations
• Added the option to schedule restarting and / or rebooting Network Devices
• Added support for WhatToMine.com as a source of profitability
• Improved overall performance (through network information caching)
• Introduced keyboard shortcuts for selecting groups of devices (CTRL+A for all devices, CTRA+A N for Network devices, CTRL+A U for USB devices, CTRL+A G for GPU devices, etc.)
• Scroll to the latest History entry on startup
• Don't consider known restarted / rebooted Network Devices "suspect"
• Fixed flicker with Stratum Proxy details
• Fixed potential for user metadata to corrupt device descriptors (rare)
• Fixed potential for WhatMine.com API code to crash (rare)
• Fixed pool information not displaying for select Network Devices (rare)
• Fixed a crash with MultiMiner Remoting discovery (rare)
• Large code restructure / rewrite (to prepare for .NET Core)

If you have any feature requests or issues please log them here:

http://issues.multiminerapp.com

And for help on using the app, see:

http://help.multiminerapp.com

As always, source code is available at:

http://source.multiminerapp.com

Finally, to learn how to contribute, visit:

http://contribute.multiminerapp.com

Happy mining!  

[nwoolls]

Happy New Year!

MultiMiner version 3.8.4 is now available for download. This release continues to improve MultiMiner's excellent support for Network Devices (AntMiners, G-Black, Raspberry Pi controllers, Spondoolies and more) with the following changes:

• Introduced optional support for scanning class A & B subnets for Network Devices
• Fixed the possibility for network scans to overlap on large subnets
• Network scanning will now find miners on the local PC
• Longer duration RPC API hashrate metrics are now preferred (works around some Network Device drivers with inaccurate response data)
• Fixed situations where a network scan may not find Network Devices (rare)
• Introduced a test for RPC API servers such as Network Device controllers (found here)
• Additional code restructure / rewrite (to prepare for .NET Core)

If you have any feature requests or issues please log them here:

http://issues.multiminerapp.com

And for help on using the app, see:

http://help.multiminerapp.com

As always, source code is available at:

http://source.multiminerapp.com

Finally, to learn how to contribute, visit:

http://contribute.multiminerapp.com

Happy mining!