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?

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

Sorry I meant to post that losing time to a DDOS attack isn't the owner's fault!   Sorry for my typo.    Having a failover pool would be excellent!   

I also lost time last night because a DDOS attack and I was sleeping.   That is the owner's fault.  It sucks not having a failover pool.

Well, anyone looking at the CDF, that 0.98 means that all pools should average one block like that or longer in every ~50 blocks.
That being the pool's 25th successful block, means it's not at all unexpected.

But at least the average since the pool started is still looking pretty good
69.52% of diff average per block.
i.e. we've found ~1.44 times the number of expected blocks so far.

A long block like that indeed affected those two numbers as I said in that post on the previous page, but that luck streak before has kept the average better than expected.
Of course if you start mining at any time, the expected long term average is 100%, but the shorter term average will of course vary a lot more.

That all being said, the one thing that makes that guaranteed variance easier to bear with PPLNS, is the higher pool hash rate.
We are slowly climbing up there, but of course the more hash rate the better
1700TH means at the moment an expected average block time of ~1day 4.25hrs so it's getting better

I have a batch 2 S2 that has been mining since 2014-04-17. I replaced the PSU with a Corsair AX1200i, other than that I'm happy with the unit. Rock solid, never goes down.

Since an S2 draws about 1kW, your farm is producing about 16kW of heat. That's a lot of heat, and I suspect that is the problem.

What temperatures are your S2s running at? Sounds like they are overheating and shutting down. Constantly having to restart them is no fun, and also doesn't solve the problem. The only way to fix this is to get better cooling (more airflow / better heat extraction / etc), or break the farm into different locations.

The good news is that your S2s will shut themselves down due to thermal limits before any damage is done. Once you improve the cooling, all your units will be rock-solid. Try this test: take one trouble unit - one that needs rebooting several times a day - and put it in a different location all by itself (with great cooling / ventilation). Take it home, or put it in a totally different room on the other side of the building, or another building, or something. If it still needs rebooting then cooling isn't your problem. But I'm 99% sure cooling is the problem. It's the major problem of any miner with a big enough farm.

I have 5 S2 and they run 24 x 7 and have never stopped.  I have updated to the latest firmware.  Why do you not call there support in Denver Co there great, instead of flaming them on a public form.

 

I was getting a ridiculous amount of HW errors last 24 hours on one blade, at one pool I was mucking with (what a dud pool, 3 days and still no confirmed payouts for BTC) anyway, i had the miner do 2 different pools balanced setting, 1 blade each, when I switched it to just a single pool and used the failover method my errors went to 0.00% that is with S3+ B8

I also have 5 S2 machines that have always ran perfect since day 1. I got them when they came out and they are still running great.

I would say you have some other issue.

No Offense.

Look at the bitcoin value. less then $480 USD per BTC  I see why the price is what it is.

not really no.. Thats just 3x 1ths boxes.. if you read their description a moonrakerwarp3 = 3x moonraker boxes. So you'll spend 12u for 3ths.. thats been done for a long time.

Dear Miasma,

We are waiting for testing results of the S4 sample machine. Hopefully there will be good news before next Tuesday.

Unfortunately the expected ROI for the sp31 is only about 1.5 btc when it comes out.   Everyone is late to the party.

Any news on the S4?

And by "S4" I mean like an S2, except using the 28nm BM1382 ASICs.