[opensuse] Network configuration enhancement
We use openSUSE in a data collection system. Many of the transducers are Ethernet (wired) based. The configuration of all these transducers (there can be dozens of them - all on their own interfaces) is a bit of a task. And, once set up, we do not want these interface configurations to be altered. So, we do not use Network Manager or wicked. Only root is expected to be changing something. (And maybe not even root). At the same time, there are other interfaces that are useful when the vehicles are not on the road. For example, a USB interface that allows access for service. Or some other Ethernet port that is used for the same activity. It depends on the system layout. Anyway, there are two classes of Ethernet interfaces: those that are essentially carved in stone and should not easily be changed, and those that are more flexible and dynamic. Currently, we have to use YaST to enable/disable one of these dynamic adapters when they are used. As they may not be present at all times (the USB variant), we cannot set up how they should be treated in any permanent fashion. Going in to YaST is something we try to avoid. And in this case, it opens the opportunity to mess up some other interface accidentally. We have been exploring, given the current openSUSE network system, how we could get the flexibility with some interfaces while maintaining hands-off with others. Primarily via udev. But that also has limitations: the interface need not be present - and when/if it is, something can be made to happen. But what happens is not flexible. Ar at least not as flexible as one can set up in, say, a KDE environment . So, I am curious: how might one mix the types of configuration appropriate for different Ethernet interfaces? This is both for existing openSUSE, and for what features might be added in the future. Like a KDE Network Interface that requires password access to modify some interfaces. Or some other brilliant method that does not mess up what currently exists. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
W dniu 15.07.2019 o 11:08, Roger Oberholtzer pisze:
So, we do not use Network Manager
Why? I think it fits exactly for what you need. I don't have experience with running lots of servers, but I have a private one with NetworkManager. You can configure it via nmcli or by editing files in /etc/NetworkManager/system-connections/ (or by nmtui for higher user-friendlyness).
Only root is expected to be changing something. (And maybe not even root).
https://developer.gnome.org/NetworkManager/stable/nm-settings.html#nm-settin... -- Adam Mizerski
W dniu 15.07.2019 o 11:27, Adam Mizerski pisze:
W dniu 15.07.2019 o 11:08, Roger Oberholtzer pisze:
So, we do not use Network Manager
Why? I think it fits exactly for what you need.
I don't have experience with running lots of servers, but I have a private one with NetworkManager. You can configure it via nmcli or by editing files in /etc/NetworkManager/system-connections/ (or by nmtui for higher user-friendlyness).
Only root is expected to be changing something. (And maybe not even root).
https://developer.gnome.org/NetworkManager/stable/nm-settings.html#nm-settin...
-- Adam Mizerski
You can also leave your existing configuration as is and tell NM not to touch it: https://developer.gnome.org/NetworkManager/stable/NetworkManager.conf.html#i...
On Mon, Jul 15, 2019 at 12:27 PM Adam Mizerski <adam@mizerski.pl> wrote:
W dniu 15.07.2019 o 11:08, Roger Oberholtzer pisze:
So, we do not use Network Manager
Why? I think it fits exactly for what you need.
I don't have experience with running lots of servers, but I have a private one with NetworkManager. You can configure it via nmcli or by editing files in /etc/NetworkManager/system-connections/ (or by nmtui for higher user-friendlyness).
Only root is expected to be changing something. (And maybe not even root).
https://developer.gnome.org/NetworkManager/stable/nm-settings.html#nm-settin...
Are you sure it applies to editing connection and not to its activation? Because quoting this link: --><-- When this is not empty, the connection can be active only when one of the specified users is logged into an active session. --><-- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Jul 15, 2019 at 11:27 AM Adam Mizerski <adam@mizerski.pl> wrote:
W dniu 15.07.2019 o 11:08, Roger Oberholtzer pisze:
So, we do not use Network Manager
Why? I think it fits exactly for what you need.
I don't have experience with running lots of servers, but I have a private one with NetworkManager. You can configure it via nmcli or by editing files in /etc/NetworkManager/system-connections/ (or by nmtui for higher user-friendlyness).
Only root is expected to be changing something. (And maybe not even root).
https://developer.gnome.org/NetworkManager/stable/nm-settings.html#nm-settin...
read-only does indeed look promising. This seems to be describing the network manager as used in Gnome. How about KDE? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
W dniu 15.07.2019 o 13:10, Roger Oberholtzer pisze:
This seems to be describing the network manager as used in Gnome. How about KDE?
This describes NetworkManager. It has a daemon, that is responsible for holding configuration and doing hard stuff. You communicate with this daemon using nmcli, gnome applet, kde plasma applet or any other client. It works the same, no matter what desktop environment you're using.
On Mon, Jul 15, 2019 at 1:21 PM Adam Mizerski <adam@mizerski.pl> wrote:
W dniu 15.07.2019 o 13:10, Roger Oberholtzer pisze:
This seems to be describing the network manager as used in Gnome. How about KDE?
This describes NetworkManager. It has a daemon, that is responsible for holding configuration and doing hard stuff. You communicate with this daemon using nmcli, gnome applet, kde plasma applet or any other client. It works the same, no matter what desktop environment you're using.
Interesting. I just need to see how to make certain interface configurations read-only. As the default is that they are not read-only, ones added on the fly should be configurable. I will report back when I have had a chance to explore. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Adam Mizerski -
Andrei Borzenkov -
Roger Oberholtzer