Quote from: MentalNomad on November 02, 2017, 09:18:54 PM

Quote from: kk003 on November 02, 2017, 06:25:04 PM

Quote from: MentalNomad on November 02, 2017, 04:59:42 PM

Can someone please provide a proper technique for re-IPing an nvOC 19-1.4 box through SSH?

kk003_telegram has code to to send public ip in case of changed (don't know if you need this feature in case your new ip is dynamic)

Useful, but not necessary - I have access to the routers and can see which IP is being picked up from DHCP.

Quote from: kk003 on November 02, 2017, 06:25:04 PM

In case you don't want DHCP here is a guide.

A example for local static ip:
sudo nano /etc/network/interfaces

.... [clip]

This looked maddeningly like something I'd tried, but I walked through it with yours as a reference and found my STUPID, STUPID BLUNDER.

Instead of :

Code:

auto enp0s31f6
iface enp0s31f6 inet static

I had

Code:

auto enp0s31f6 iface enp0s31f6 inet static

Not sure if it stemmed from a copy/paste error of my template, or just a stray accidental backspace or deletion, but I didn't spot it until comparing your text to mine, so, thanks! It's something of a relief to know I wasn't entirely on the wrong track.

I'm also amused that we have the same network interface adapter. Note to others following along: you may have a different interface, like enp4s0 instead of enp0s31f6. You can look yours up with the command ifconfig.

Moving on....

Quote from: kk003 on November 02, 2017, 06:25:04 PM

then stop network manager:

Code:

sudo systemctl stop network-manager.service

Remove it from system startup:

Code:

sudo systemctl disable network-manager.service

Is that step strictly necessary? I edited the interfaces file and rebooted the box, and it came up on the desired IP. What does killing network manager achieve?

Quote from: kk003 on November 02, 2017, 06:25:04 PM

Update: I assume you know how to connect to your rigs using ssh and have a well configured router if you are behind one

Yes, I'm fine on that front - but good to mention for others following along.

Thanks, again!

Yeah, silly things happens from time to time with linux's files Angry

.
Others are:
line that does not end with end of line
tabs that should be spaces (and the other way round)
no blank line at end of file (like hosts.allow and hosts.deny)

Network managers usually cause problems when a static ip config is used, such as in CentOS.
If you decide to leave it on, I think you should watch it for a while at least.
Maybe in Ubuntu does not cause problems but I could not say.
I have it disabled myself.

About the interface probably we both have a H110 pro BTC+