I didn't change any IPv6 settings with nvOC. I'm not sure what the problem might be. If you figure it out let me know, so I can apply it for the next version.
The cmd:
(might help solve the problem, but probably not)
The cmd:
Code:
sudo dhclient -v -r
(might help solve the problem, but probably not)
As you guessed, it didn't help.
Quote
there is a website:
test-ipv6.com
it attempts to help you identify the source of IPv6 problems; it might help, but probably will only tell you what you already know.
test-ipv6.com
it attempts to help you identify the source of IPv6 problems; it might help, but probably will only tell you what you already know.
I tried bringing this up in Links, but it needs JavaScript to work. I'd need to move the rig closer to where I can plug in a monitor, keyboard, and mouse to see what SJWfox says...maybe tomorrow, as I also want to move nvOC off of an SD card in a USB reader stick to the mining rig's M.2 SATA SSD.
In the meantime, I've gotten enough of a workaround set up that (1) apt-get upgrade works and (2) I have an auto-switcher up and running, as mentioned in my previous post.
It will be nice when there is no more NAT to deal with; although there will need to be better parameter security.
This afternoon, I knocked together a simple profitability auto-switcher that works with nvOC and NiceHash:
https://gitlab.com/salfter/nvoc-nicehash-switcher
It might also work if you're mining elsewhere, though profitability is determined by NiceHash (as exposed through their API). It's a Python script that gathers information about what's profitable and calls shell scripts to reconfigure overclocking settings and launch miners on a per-algorithm basis. It replaces oneBash for normal operation; oneBash is only needed for initial setup or to add/remove GPUs (it manages /etc/X11/xorg.conf).
https://gitlab.com/salfter/nvoc-nicehash-switcher
It might also work if you're mining elsewhere, though profitability is determined by NiceHash (as exposed through their API). It's a Python script that gathers information about what's profitable and calls shell scripts to reconfigure overclocking settings and launch miners on a per-algorithm basis. It replaces oneBash for normal operation; oneBash is only needed for initial setup or to add/remove GPUs (it manages /etc/X11/xorg.conf).
Nice work
I will integrate this into the next oneBash / v0018.
I will keep your default BTC address and ensure it is clear you implemented the instantaneous profit switching algorithm.
I do think with when using different algos in makes sense to have different clocks; however I don't think the settings for those should be spread out over a bunch of different bash files.
I will bring all the settings inside oneBash and make a:
SALFTER_NICEHASH_PROFIT_SWITCHING="YES" YES / NO switch
Using your implementation; it should only require a few modifications to implement other targets such as 'lowest difficulty out of a given set of coins' and more.
Thanks for providing another tool to the community,
This is an AWESOME idea! I was curious though, do you really make more it being converted to BTC right away or mining the coins directly? Anyone with some feedback would be greatly appreciated.