Single server, no GUI. How to configure the static IP details?

English Install/Boot/Login
1

Hi Folks,

Happy New Year to you all.

I’m sorry to bring the old “YAST” question up once again but as a non trivial user of SLES and openSUSE for a couple of decades I am failing to see the benefit of the loss of YAST, even if it received no support or development.

Let me take my use case and see what folk can come up with.

In a DMZ I have a LEAP server running an HAProxy - it will handle all traffic etc. That sits in a DMZ with a private LAN and there is only 22/80/443 traffic allowed. The system was installed and picked up a DHCP IP Address that is garbage, but hey that’s why we can download and use the full DVD image for building. There is no GUI and there is no valid networking details so you cannot connect remotely, but the Virtualisation system can give you access to the console - Brill. Where previously I would have typed “yast lan” and be fixed and away in 60 seconds, now… Well what does one do? Myriyn wants a GUI (not happening in this millennium) and there no way of connecting with cockpit so what??

To my mind the stopping of development makes sense, but the removal of what already exists is like removing a SQL view, suicidal! The single biggest differentiator between SUSE and other distributions is gone (not the only one, but the biggest)

Looking forward to the incoming fire :grinning:

Take care,

Tim

2

Hi, Cockpit or nmtui. I use the Cockpit flatpak on my main system and can connect over ssh to any system and manage. Nothing needs to be installed on the remote system. You can install the local version and connect via a web browser.

3

I assume Leap is using NetworkManager?

Or is it using systemd-networkd?

wiki.archlinux.org/title/Systemd-networkd

4

See release notes:

NetworkManager is now the only network configuration stack in openSUSE Leap 16.0.

5

Hi Malcolm,

When the LAN is the problem, cockpit can’t connect to fix what is broken. I do like cockpit overall and in the majority of cases it’s use is better than a local copy of YAST - hence why I can accept that development can stop.

nmtui has always seemed to me to be a poor man’s (read Trabant style poor) version of YAST - kind a sucks. I have to use that with Alma and Rocky and I aways feel slightly unclean afterwards. I hadn’t realised that it was now included, I suppose that’s a relief and we should make that more obvious.

cheers,
T

6

nmtui is better as Malcolm said.

The docs need to be updated as Network Manage is not the only configuration tool included :rofl:

T

7

@timscotland You do realize it’s just a flat file /etc/NetworkManager/system-connections/ and can be a drop in? I use that on MicroOS and combustion…

So you don’t really need any tools, well vi works :wink:

cat /etc/NetworkManager/system-connections/em1.nmconnection 
[connection]
id=em1
permissions=
interface-name=em1
type=ethernet
[ipv4]
method=manual
address1=192.xxx.xxx.xxx/24
gateway=192.xxx.xxx.xxx
dns=xxx.xxx.xxx.xxx,xxx.xxx.xxx.xxx
8

My first issue is that the younger folk want nano rather than vi (there is no hope for the world!)

Then there is “The one” who has to be taught everything and can’t self train and YAST was so useful…

I wonder if HR would accept "Being made redundant because of LEAP 16… " tempting :stuck_out_tongue_winking_eye:

T

9

Just to clarify: nmtui and nmcli are both text-based UIs that talk to the same NetworkManager service, and the graphical applets (for GUI environments).

10

Please clarify. All 7 of my 16.0 installations run on systemd-networkd (with static IPs), and NetworkManager is not installed.

11

Yes, that’s a bit misleading. In openSUSE Leap 16, NetworkManager is the default framework for managing network connections, particularly on desktops. That’s what the release notes are highlighting. On a fresh Leap 16 install, NetworkManager is installed and enabled by default. On an upgrade, the previous network stack (wicked, systemd-networkd, or even NetworkManager if it was already in use) usually stays active.

Users are free to install “systemd-networkd” if they would prefer.