Source: https://linuxize.com/post/how-to-setup-passwordless-ssh-login/
This tutorial is a basic rundown of commands. Check the source referenced above for more detail. Or use your favorite internet search engine.
Your SSH server (pimp machines) are only as secure as your passphrase. Also, it's just plain annoying to type the damnable thing at every login or file transfer. Fix it with passwordless login key exchange and disable passwords at login.
For the purposes of this tutorial, I will use $CLIENT to indicate the machine you SSH from and $HOST to indicate the machine you SSH to. Commands will be couched in code blocks
$HOST > like this
$CLIENT # and this
a prompt ":>" is a non-root prompt, while "#" is root user. Yours may be different (probably is, at least for non-root) in your shell config file and need to adjust your reading accordingly.
I'll be using <CLIENT_IP> and <HOST_IP> to indicate where IP addresses for the machines should be substituted. If you have changed your host name in ($HOST)/etc/hostname, and have added your pimp rig to your $CLIENT/etc/hosts or have configured your router to respect hostnames on your LAN, you can use the hostname instead. (I configure all three to take no chances, and configure a fixed-IP for my rigs. LAN best practices.)
01. Check for existing SSH key pair. ($CLIENT)
$CLIENT :> ls -al ~/.ssh/id_*.pub
If this command returns one or more file names, you already have SSH keys and can skip to step 03. Or you can create a separate set of keys, but that's beyond the scope of this tutorial.
02. Generate SSH key pair ($CLIENT)
$CLIENT :> ssh-keygen -t rsa -b 4096 -C "some_email@some_domain.com"
The keygen process will ask where to store the keys. The default location is ideal unless you have a compelling reason to change it.
Follow the prompts. The process should be complete when you are returned to your shell prompt. Still, you should verify that the files were created.
$CLIENT :> ls ~/.ssh/id_*
You should have an id_rsa and id_rsa.pub.
03. Push keys to $HOST
Your $HOST needs a copy of the public key. You can do this manually (details not in this tut) but the ssh client package provides an easy way to do this.
By default, pimpos wants us to use the root user. Unless you have created and use a regular user (with sudo or doas privileges) (which you should do because logging as root, especially over the network, is bad bad admin practice.) This tut, however, assumes you have not changed this practice. If you have (good for you!), you will need to modify the login appropriately.
$CLIENT :> ssh-copy-id root@HOST_IP
SSH will ask for your pimp passphrase and copy the public key of $CLIENT to the $HOST.
05. Verify all went well.
$CLIENT :> ssh root@HOST_IP
You should be presented with your pimp shell prompt and not be asked to enter the passphrase. If you configured the ssh key with a passphrase, you will be asked for it.
04. Disable $HOST password login. (optional but recommended)
After verifying you can log into an account with administrative privilege (root or user with sudo or doas permission), you can secure your $HOST by disabling password authentication.
Log in to your $HOST (hurray! no password) and edit the file /etc/ssh/sshd_config.
Search for and modify the following lines so they match.
PasswordAuthentication no
ChallengeResponseAuthentication no
UsePAM no
Save and close the file. Now you need to restart the ssh server process.
$HOST # systemctl restart ssh
Done. Happy administering.
Sidenote if you aren't sure if your CPU has the ability to use the "1Gb pages" and you don't want to check on your CPU's vendor website documentation, use the quick command below.
lscpu | grep -w "pse|pdpe1gb"
If the "pdpe1gb" cpu instruction is listed the the software should be able to use it for mining. If this instruction is listed then the cat is dead and the software can't use it even if you enable the option in the software configuration (ie: XMRIG "1gb-pages" value)
To get your Watts showing more accurately, there are some things you can adjust yourself.
By adding Watts to the fields below manually, you can get it to match the power usage AT THE WALL (if you have a meter of course). I have mine set to “compact view” to show me all the goodies. 😉
For example…
Your main MinerFarm “view” screen.
There are two baseline power fields. One on the miner and one for the rig/actual PC or system.
Miner View Baseline Power is only used for miners that do not report their power usage.
If you know you GPU is using 100w of power but your chosen miner is not reporting and thus showing 0’s or nothing, this is where you would enter 100. If you have 6 x GPU’s, and you know each is using 100w, enter 600 in here.
For example…
When you click on one of your miners (above image, 3rd line down, Production Rig 1) you’ll see something like the below. Down the bottom right is where you add this. It’s worth mentioning that the Watts displayed on this screen are the Watts used by the device/s for mining. In my case below, the Watts that the GPU’s are using.
The Host Power Baseline is for the rig's overhead power (CPU/MB/RAM/SSD/PSU/Riser Cards) (i.e. Things not reported via a miner.)
For example…
When you click on “Admin” on the left navigation tabs you will see something like the below.
Then click on the Agent you wish to amend from the above ie, I’ll stick with my Production Rig 1 on the 2nd line, and again, see below screenshot, down the bottom right you would add your base watts here for that Rig/PC/System.
Now your Watts aka power usage should be pretty right.
As always.. if anyone needs assistance.. please jump on the chat in Discord and a friendly fellow PiMP will be glad to help out.
Happy mining all. 😊
Builds and installations, photos and guides. Show off your build!
66
Topics
149
Posts
Hello pimps I am sharing some talks we had about this in discord, hope it helps someone:
pimp currently supports many usb asic andsoon monitor network asic too
ASIC:
4x GekkoScience 2Pac
1x NF1 Nanofury
1x Futurebit Moonlander 2
here is what it looks like on the rig
[/root/bbb/extras]:# pimp --add asic
Profile list filtered by "asic":
ID Name
5101 (asic) bfgminer: for usb gridseed/asics [bfg.gsd.conf]
5102 (asic) bfgminer: for usb zeus/asics [bfg.zeus.conf]
5151 (asic) bfgminer: for usb futurebit asics [bfg.futurebit.conf]
5211 (asic) cgminer-dmaxl: for usb gridseed asics [cgminer.gsd.conf]
5221 (asic) cgminer-dmaxl: for usb zeus asics [cgminer.zeus.conf]
5301 (asic) cgminer-gekko: for usb gekkoscience 2pac asics [cgminer.gekko.conf]
5321 (asic) cgminer-ckolivas: for usb nanofury SHA-256 asics [cgminer.nanofury.conf]
Usage: pimp --add [Profile ID]
those are the miners designed for asic use (cgminer and bfgminer) and the clones of them, and they build those cgminer versions specially for some hardware to get good hashrates, i think too
For the complete list of PiMP Profiles, miners and confs, and how to use them, check out this post: https://forum.getpimp.org/topic/10/setting-up-miner-profiles
Q: Any to avoid? I saw some USED on ebay. I wasn't aware of an after-market for ASICs. I went with GPU mining as I can and do sell used for
asics are usually semi profitable the sooner you get them but as more asic released for a coin then the diff goes up because everyone mines with so used asic usually for fun, learning, and if you have cheap power, a little more. mostly if you are a believer that the coins will go up then you value them even if take a slight loss due to electrics yes there are several SHA-256 algorithm coins
also great for fun & learning. For $50 you could play with one or two.
TLDR: if you look at the ones that use cgminer / bfg miner you will be in good shape
some of the team have androids and other miners that are being picked up by miner.farm - coming soon
Happy mining pimps!
How to solve problems with hardware, software, and how to fix mining issues.
290
Topics
1724
Posts
Thanks to accessdenied for info in the miner.farm discord chat!
If you are mining with claymore on AMD, and you are all of a sudden getting a dag error:
"GPU0 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
GPU0 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
GPU 0 failed"
Editing the pcfg file and placing -eres 1 in the FLAGS= line in claymore-dual.pcfg seems to fix the issue.
From Claymore-dual documentation:
-eres this setting is related to Ethereum mining stability. Every next Ethereum epoch requires a bit more GPU memory, miner can crash during reallocating GPU buffer for new DAG. To avoid it, miner reserves a bit larger GPU buffer at startup, so it can process several epochs without buffer reallocation. This setting defines how many epochs miner must foresee when it reserves GPU buffer, i.e. how many epochs will be processed without buffer reallocation. Default value is 2.
Cryptocurrencies have been getting quite popular in the Caribbean region and in Antigua and Barbuda, the island has seen significant growth. Crypto adoption has been on the rise in the island country and just recently, a regional news report detailed that more than 40 major businesses are accepting bitcoin cash for goods and services. During […]
The post Caribbean Crypto Hotbed: More Than 40 Businesses Accept Bitcoin Cash in Antigua appeared first on Bitcoin News.
https://news.bitcoin.com/caribbean-crypto-hotbed-more-than-40-businesses-accept-bitcoin-cash-in-antigua/
We promise to keep your email safe and never spam you.
