23.10.2018 21:05, Paul Groves пишет:
On 23/10/2018 18:48, Andrei Borzenkov wrote:
Check /etc/udev/rules.d (70-persistent-net.rules is the primary suspect)
Does not exist paul@media:~$ ls /etc/udev/rules.d/ 70-snap.core.rules
for any file that contains eno1. Also check *.link files in various directories (/lib/systemd/network/, /etc/systemd/network; see "man systemd.link" for full list).Apparently both your interfaces are configured to have name "eno1".
Nothing in these files: paul@media:~$ cat /lib/systemd/network/* | grep eno1 paul@media:~$ ls /lib/systemd/network/ 80-container-host0.network 80-container-ve.network 80-container-vz.network 99-default.link
Empty: paul@media:~$ ls /etc/systemd/network/
That would explain the problem if they are configured to have the same name.
What should I be looking for in man systemd.link?
And please do it onhttps://susepaste.org/, not on some commercial site. That is my own server actually. I can see it from here :)
I never heard of susepaste.org
I am going to confuse the matter more now. I just rebooted the system and now the two NICs are reversed. The primary NIC is now called rename2 and is no longer working. The second NIC which has not worked until no is now called eno1 and is working fine. :?
That just enforces theory that it is firmware problem. Provide information I asked for here and in another reply in this thread. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org