Topic: [ mining os ] nvoc - page 143. (Read 418546 times)

Yes, that's set to "YES". I should also mention that I've never mined ETH, so that makes it even more strange that it automatically switch to ETH when I turn on the WTM and choose my coins.

You will need to make sure you have this set in 1bash as well:

Hi there! I thought i was going to try WTM switch today. But I ended up with a strange problem..

I got i set up exactly like this:

But it starts mining ETH.. Can't stop scratching my head..
I bet it's something simple, but to hard to find the problem for a novice like me 

I compiled this up for nvOC about a month ago. You can find it here:


http://www.cstone.net/~stu/nvOC/ccminer-2.2.2-tpruvot.tar.gz


Edit: I compiled it up using only the arch flags for the 10x nvidia cards:

Hope this helps.

Thanks papampi. I've got it set to:

In bash every thing after # is not readable by scripts
So your setting is gonna be some thing like this

Another dumb, probably already answered question from me. Can someone answer, or point me to the answer to:

For the WTM_AUTO_SWITCH_COINS= option, is the comments area the exhaustive list? i.e. "ZEC;ETH;ETC;XMR"

Since I have ZEN in mine, I am guessing the answer is no. If no, is there an exhaustive list, and valid syntax documented somewhere?

Thanks for your patience.

All really good OS-side hardening. My biggest question is, by doing so, are there any impacting issues any of that would have on the mining functionality? Also, it might be good for the devs here to implement those changes (you know, if they are looking for something more to do, lol.

I'm normally a windows guy. Can you please publish a guide how to compile stuff like this in ubuntu? I always get an bignum error. Thanks a lot.

It's tpruvot official version. I'm using windows version, about one week without problems, mining with EVGA 1080ti.
Link to miner:
https://github.com/tpruvot/ccminer/releases

Thank you.

Can you please post come details of it, like what fork it is and the link for that.

I will try to compile and test it. Thanks.

Hi. The easiest way from my point of view is get yourself an Bittrex account. In the LAB menu switch on auto exchange for all the coins you like to exchange. Use the Bittrex wallets on all your pools. Let WTM autoswitcher do its job. done!

Hi, for xzc(Zcoin) there are new version ccminer 2.2.2 with fixed hashrate and added --submit-stale option.
And in config file, for xzc mining in pool like miningpoolhub and suprnova, there are no intensity option. Please add in future update. Thank you!

Well, in simple terms, it doesn't convert into BTC or any other coin.

It simply checks what is the current profitable coin, then switches the mining and mines that current profitable coin according to the individual coin setups provided in 1bash. PERIOD.

The instructions are pretty clear in 1bash, not sure what you expecting, please elaborate (perhaps, it is difficult for me to understand what people actually expecting to see as I know IN & OUT of it mostly, so finding it difficult to understand the end user point of view).

See below and let me know if you think we need to add something to the below instructions, so we will add it in the further versions which would eventually help others.

Good Morning,

is there any good config out there where the Pampampi WTM Auto Swtich is explained.

Just to get it right for me...

1. They're are pools like nicehash that direct convert my hashpower into btc

2. algo switching pools like mining pool hub

3. and now the important one... WTM Auto Switch

but to get the most out of it, the coin actual has to be converted to into some bigger coin like
btc or now bch direct to profit from the coin auto switch?

Please correct me and/or show me the right way that I can test and use the auto switch. I already have my walltes up for the most coins like ZEC, BTCZ, HUSH, MONA, ZEN, VTC, FTC, GRS.

I know this is not an easy task to show, but I whould realy appreciate it couse I dind't found a think how to do it right.

Regards!

WORKS LIKE A CHARM!!!

Thanks Alot you're the Genie of my life please came out the lamp 

If you know your way around your OS, hardening the system is not that hard. Really.

Center for Internet Security is legit and a good place to start: https://learn.cisecurity.org/benchmarks
look for Ubuntu Linux 16.04 (CIS Ubuntu Linux 16.04 LTS Benchmark version 1.0.0)

• Do not redirect any traffic to the miners. EVER. NEVER use Windows for access to anything you actually value. It's gotten better, but it's still not safe enough to be used to guard the castle.
  
• If you want to set up a jump server, make it multi-homed. This means that there is one interface plugged into the public network (User Network above) and one interface plugged into the private network (Miner network above). If you can not do this, or do not want to create a multi-homed machine, use a single homed machine and use the router to redirect port 22 to that single-homed machine.
  
• Do not use passwords alone for users. Use public/private keypairs instead. If you want to be even safer, implement multi-factor authentication. Rudimentary multi-factor authentication can be a combination of public/private keypairs and a password. Here is some good info: https://sysconfig.org.uk/two-factor-authentication-with-ssh.html
  
• If you want to secure the miner, since nvOC is based on ubuntu 16.04, use the built-in security tool known as ufw or iptables:  https://help.ubuntu.com/lts/serverguide/firewall.html
  
• Lock down all inbound ports except for port 22 (ssh). Restrict outbound traffic such that you only allow traffic outbound that you know/trust. Know what ports and protocols need to be opened. If you are new to the game, some experimentation will be necessary. If you see a port open and you don't know what it is, close it and see what breaks.
  
• If you want to have something running that provides a pretty interface, make sure that the provider of that information can only run in userspace and can not escalate privileges to root. How to do that? Implement sudo properly with a well constructed sudoers file that limits what commands a giver user can execute as root. Make sure that the user that the provider (web server) runs as does not have a real login shell.
  
• If you need to use Windows Remote Desktop, tunnel it through ssh so it is at least encrypted.
  https://www.saotn.org/tunnel-rdp-through-ssh/
  

System/Network Security

As a security nerd, I am going to attempt to add value to this thread. Since updates are turned off, and there's a pretty wide attack surface, I've been thinking about how to keep my miner(s) isolated from the rest of my systems except for some remote access. Here are some initial thoughts:

- Without hardening the system, I need to put some network access control function/device between my user network and the miners.
  - I have an old broadband router that I can put them behind with the "internet side" facing my internal network.
    - Have the "broadband side" configured with a static IP address on my user network
    - Open TCP/22 (for ssh and scp) and redirect it to the first miner. You can use that one as a jump-box to get to the others
    - Open TCP/3389 (Windows Remote Desktop) and have that directed to a Windows box (old laptop perhaps) and use that as a jump-box for about anything
  - I actually have several actual firewalls (Forcepoint/Sidewinders and a Palo Alto Networks) that can segment the network for me, not to mention IPS, etc.
    - Open the same ports as above?

ASCII Network Diagram

Internet --> Main firewall --> User Network (where my workstations and servers are) --> Miner Firewall/Broadband-router --> Miner Network

Are there any recommendations on OS hardening you could recommend?

FWIW, I FTP it (2unix and 3main too) to one of my servers. You can also scp it.

All noob issues on my part. No, ext3/4 partitions cannot be read by a Windows box without a helper. The other partition needed to be formatted, then magically the 1bash file showed up on it. The latter was a little strange, but all good so far.

Now, if I can wait for the new version that supports integrated video so I stop throwing xorg errors.