NEMS 1.5 - static IP with NetworkManager & cockpit

[spacej]

If you would like to set up a static IP for NEMS 1.5 (should also work for 1.4.x) the following steps might help you.
Additionally, the last command installs the interface for Cockpit to NetworkManager, enabling IP changes via the Cockpit-Webinterface.


ssh into into your NEMS machine and execute the following:
(BOLD for returns)

sudo systemctl disable dhcpcd
sudo systemctl enable networking

sudo nmcli device

DEVICE  TYPE      STATE      CONNECTION
eth0    ethernet  unmanaged  --
lo      loopback  unmanaged  --

sudo nmcli connection

NAME  UUID  TYPE  DEVICE

sudo mv /etc/network/interfaces /etc/network/interfaces.unused
sudo nmcli connection add type ethernet ifname eth0

Connection 'ethernet-eth0' (YOUR-UUID) successfully added.

sudo nmcli connection edit ethernet-eth0
goto ipv4
set addresses YOUR-IP
set gateway YOUR-GATEWAY-IP
set dns YOUR-DNS-IP
save

Connection 'ethernet-eth0' (YOUR-UUID) successfully updated.

quit

sudo apt install cockpit-networkmanager
sudo reboot

---snip snap---

Enjoy... 

[Robbie Ferguson]

Hi spacej,
Thank you :)

Just a heads up: cockpit-networkmanager was introduced in NEMS Linux 1.5 Build 7 for Raspberry Pi.

So just for future forum visitors, note that any NEMS Linux builds after March 16, 2019 already include this, pre-configured out of the box (a bit differently than described above), so these steps posted above only apply to older builds.

Please see the documentation here: https://docs.nemslinux.com/networking

[fightgerman]

Hi spacej,
Thank you

Just a heads up: cockpit-networkmanager was introduced in NEMS Linux 1.5 Build 7 for Raspberry Pi.

So just for future forum visitors, note that any NEMS Linux builds after March 16, 2019 already include this, pre-configured out of the box (a bit differently than described above), so these steps posted above only apply to older builds.

Please see the documentation here: https://docs.nemslinux.com/networking basket random

I can see a lot of interesting information! My switches (Ubiquiti) appear to be unaffected. I realize it's not the most elegant solution, but it gets the job done. It reduces the footprint of Nems and makes it easier to deploy.

Since we're on the subject of motioning, this also works well (even with a pi zero) for packet capture with Tshark or something similar, especially if your switches support mirror port.