Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am using OpenSUSE Leap 42.2 on a Dell Inspiron 1545.
There is an error when I change from eth1 to eth0 after deleting another entry:
"key given for udev rule is not supported"
When I searched those quotes on Google, it showed no results. Am I the only one that has this problem?
How do I fix this? Why don't they have an automatic problem detector that shows problems?
Last edited by ComputerCritic; 05-15-2017 at 02:18 PM.
Reason: To add information.
First, just to clarify - YaST Network Settings is used for configuring when wicked is used for network management rather the Network Manager, so I assume you are wishing to use wicked? (The former is similar to the old traditional ifup method of controlling network interfaces).
There are entries added automatically to /etc/udev/rules.d/70-persistent-net.rules to designate the eth* naming based on device MAC addresses. The following commands should confirm the association...
I am using OpenSUSE Leap 42.2 on a Dell Inspiron 1545.
There is an error when I change from eth1 to eth0 after deleting another entry:
"key given for udev rule is not supported"
When I searched those quotes on Google, it showed no results. Am I the only one that has this problem? How do I fix this?
Read the "Question Guidelines" link in my posting signature. You say you 'change from eth1 to eth0 after deleting another entry'...but don't tell us where you did this, how, what you clicked on/typed in. We can't guess. You can easily go into YAST, and change your network management from wicked to NetworkManager, and get the GUI that you seem to want in the system tray.
Quote:
Why don't they have an automatic problem detector that shows problems?
Because they don't exist, for any computer or operating system, anywhere, and probably won't in our lifetimes. If you're so unhappy with Linux, why do you persist in using it?
Read the "Question Guidelines" link in my posting signature. You say you 'change from eth1 to eth0 after deleting another entry'...but don't tell us where you did this, how, what you clicked on/typed in. We can't guess. You can easily go into YAST, and change your network management from wicked to NetworkManager, and get the GUI that you seem to want in the system tray.
Because they don't exist, for any computer or operating system, anywhere, and probably won't in our lifetimes. If you're so unhappy with Linux, why do you persist in using it?
Deleting an entry and changing eth1 to eth0 was in YAST. Before that, I was using virbr0 or whatever it is, and somehow eth0 changed to eth1
Why don't they make it so settings from both NetworkManager and YAST(Wicked) be used at the same time? Some things cannot be done with networkmanager, so I have to change between them with settings over and over?
The final one, maybe I miscommunicated.
Deleting an entry and changing eth1 to eth0 was in YAST. Before that, I was using virbr0 or whatever it is, and somehow eth0 changed to eth1
I wonder if you may have had a stale config in /etc/sysconfig/network/ifcfg-*. Start by sharing
Code:
/sbin/ifconfig -a
Code:
ls -l /etc/sysconfig/network/ifcfg-*
and we can advise from there.
Quote:
Why don't they make it so settings from both NetworkManager and YAST(Wicked) be used at the same time?
The former is used to allow regular users to connect to network environments that may change frequently (eg laptop in various wireless environments), while the latter is for more static network environments (eg desktop or server environments). Having both enabled concurrently can cause issues as they will both attempt to control given network interfaces.
Some things cannot be done with networkmanager, so I have to change between them with settings over and over?
You should elaborate with respect to what you are trying to achieve. NetworkManager can do most things that regular users might need to do. It even has a dispatcher script facility that can be used to perform quite complex operations if necessary.
Deleting an entry and changing eth1 to eth0 was in YAST. Before that, I was using virbr0 or whatever it is, and somehow eth0 changed to eth1
No, not 'somehow'....you changed them.
Quote:
Why don't they make it so settings from both NetworkManager and YAST(Wicked) be used at the same time? Some things cannot be done with networkmanager, so I have to change between them with settings over and over? The final one, maybe I miscommunicated.
Nope, sorry. Anything that can be done with wicked can be done with the CLI or network manager. They are all different utilities that do the same thing.
I wonder if you may have had a stale config in /etc/sysconfig/network/ifcfg-*. Start by sharing
Code:
/sbin/ifconfig -a
Code:
ls -l /etc/sysconfig/network/ifcfg-*
and we can advise from there.
The former is used to allow regular users to connect to network environments that may change frequently (eg laptop in various wireless environments), while the latter is for more static network environments (eg desktop or server environments). Having both enabled concurrently can cause issues as they will both attempt to control given network interfaces.
You should elaborate with respect to what you are trying to achieve. NetworkManager can do most things that regular users might need to do. It even has a dispatcher script facility that can be used to perform quite complex operations if necessary.
I agree with wicked and network manager being separate as to not cause conflict, and that network manager can do most things. Truth in your words.
Nope, sorry. Anything that can be done with wicked can be done with the CLI or network manager. They are all different utilities that do the same thing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Problem with YaST Network settings
