[opensuse] For ethernet, what does "device unconfigured" mean
I have run Yast2, and all appears happy. I have looked at files in /etc/sysconfig/networking and /etc/wicked, and all appear happy in my humble opinion. What is making the decision that these devices are unconfigured. What does unconfigured mean? Is there a single field in one of the files that has been omitted? It is very frustrating to not be able to get on the net from a machine that used to have no problem. Especially since the net is required to send details to this list. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
don fisher composed on 2015-12-27 19:12 (UTC-0700):
I have run Yast2, and all appears happy. I have looked at files in /etc/sysconfig/networking and /etc/wicked, and all appear happy in my humble opinion. What is making the decision that these devices are unconfigured. What does unconfigured mean? Is there a single field in one of the files that has been omitted? It is very frustrating to not be able to get on the net from a machine that used to have no problem. Especially since the net is required to send details to this list.
I can't tell you what's wrong. I'm running a less than a day old Leap installation, have working ethernet, and get this: # wicked show config ifstatus: no matching interfaces But, I also get this: # rpm -qa | grep wicked libwicked-0-6-0.6.28-3.1.x86_64 wicked-0.6.28-3.1.x86_64 wicked-service-0.6.28-3.1.x86_64 # systemctl list-unit-files | grep icked wicked.service enabled wickedd-auto4.service enabled wickedd-dhcp4.service enabled wickedd-dhcp6.service enabled wickedd-nanny.service enabled wickedd.service static # cat /proc/cmdline ...ipv6.disable=1 net.ifnames=0... # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether ##:##:##:##:##:## brd ff:ff:ff:ff:ff:ff inet 192.168.###.###/24 brd 192.168.0.255 scope global eth0 valid_lft forever preferred_lft forever I see nothing in YaST2 network that would stop me from deleting or changing the fixed IP configuration for eth0. Maybe you could switch eth0 to fixed IP, then work on getting wlan to work if you actually need it. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zondag 27 december 2015 19:12:20 schreef don fisher:
I have run Yast2, and all appears happy. I have looked at files in /etc/sysconfig/networking and /etc/wicked, and all appear happy in my humble opinion. What is making the decision that these devices are unconfigured. What does unconfigured mean? Is there a single field in one of the files that has been omitted? It is very frustrating to not be able to get on the net from a machine that used to have no problem. Especially since the net is required to send details to this list.
Don
An unconfigured Ethernet device means that the system detect a hardware Ethernet device with a specific MAC address and does not find a matching configuration, ifcfg-ethX file. The udev system matches your hardware Ethernet device with the name eth1, but you do not have a file ifcfg-eth1. Same goes for your wireless device. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/28/2015 10:19 AM, Freek de Kruijf wrote:
Op zondag 27 december 2015 19:12:20 schreef don fisher:
I have run Yast2, and all appears happy. I have looked at files in /etc/sysconfig/networking and /etc/wicked, and all appear happy in my humble opinion. What is making the decision that these devices are unconfigured. What does unconfigured mean? Is there a single field in one of the files that has been omitted? It is very frustrating to not be able to get on the net from a machine that used to have no problem. Especially since the net is required to send details to this list.
Don
An unconfigured Ethernet device means that the system detect a hardware Ethernet device with a specific MAC address and does not find a matching configuration, ifcfg-ethX file. The udev system matches your hardware Ethernet device with the name eth1, but you do not have a file ifcfg-eth1. Same goes for your wireless device.
How does one fix this. I do not have eth1 any more. I deleted it and started over thinking all would be set up correctly. Why does the udev system want to match Ethernet MAC address to eth1, and not use eth0? I see no reference to a MAC address in the ifcfg file. I only have a single Ethernet adapter in the laptop. Also a single wireless adapter. Is there some place I can read more about this? Thanks Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 28/12/2015 19:40, don fisher a écrit :
How does one fix this. I do not have eth1 any more.
what do yast say? network tab "general", is it wicked or network manager? may be the config file are not the same jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
don fisher composed on 2015-12-28 11:40 (UTC-0700):
An unconfigured Ethernet device means that the system detect a hardware Ethernet device with a specific MAC address and does not find a matching configuration, ifcfg-ethX file. The udev system matches your hardware Ethernet device with the name eth1, but you do not have a file ifcfg-eth1. Same goes for your wireless device.
How does one fix this. I do not have eth1 any more. I deleted it and started over thinking all would be set up correctly. Why does the udev system want to match Ethernet MAC address to eth1, and not use eth0? I see no reference to a MAC address in the ifcfg file. I only have a single Ethernet adapter in the laptop. Also a single wireless adapter...
Look in /etc/udev/rules.d/ for a file 70-persistent-net.rules It is probably there assigning the MAC address you want on eth0 to eth1. Likely it has two assignment lines. Just changing the assignment on the right address, a single character edit, and deleting the other line should be all you need to do before rebooting to find what you expected in the first place. Adding a zero byte file 80-net-setup-link.rules in rules.d/ might help to avoid future perplexity. See (near its bottom): http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/28/2015 12:05 PM, Felix Miata wrote:
don fisher composed on 2015-12-28 11:40 (UTC-0700):
An unconfigured Ethernet device means that the system detect a hardware Ethernet device with a specific MAC address and does not find a matching configuration, ifcfg-ethX file. The udev system matches your hardware Ethernet device with the name eth1, but you do not have a file ifcfg-eth1. Same goes for your wireless device.
How does one fix this. I do not have eth1 any more. I deleted it and started over thinking all would be set up correctly. Why does the udev system want to match Ethernet MAC address to eth1, and not use eth0? I see no reference to a MAC address in the ifcfg file. I only have a single Ethernet adapter in the laptop. Also a single wireless adapter...
Look in /etc/udev/rules.d/ for a file
70-persistent-net.rules
It is probably there assigning the MAC address you want on eth0 to eth1. Likely it has two assignment lines. Just changing the assignment on the right address, a single character edit, and deleting the other line should be all you need to do before rebooting to find what you expected in the first place.
Adding a zero byte file
80-net-setup-link.rules
in rules.d/ might help to avoid future perplexity. See (near its bottom): http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface...
There are just two lines in 70-persistent-net.rules. Both have an ATTR(address) entry, but the ATTR(dev_id)=="0x0 and the ATTR(type)=="1". I have forgotten how to determine the MAC address. lspci shows a lot of info, but no mac address. lsattr on the troublesome machine has entries like ------./70-persistent-net.rules while on my functioning machine I get: ---------------- ./scripts ---------------- ./if-up.d ---------------- ./if-down.d ---------------- ./providers ---------------- ./routes ---------------- ./routes.YaST2save ---------------- ./ifroute-wlp11s0 ---------------- ./ifcfg.template ---------------- ./dhcp ---------------- ./ifcfg-enp9s0 ---------------- ./ifcfg-wlp11s0 ---------------- ./config ---------------- ./ifcfg-lo Any more suggestions? Thanks Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
don fisher composed on 2015-12-28 14:37 (UTC-0700):
Felix Miata wrote:
don fisher composed on 2015-12-28 11:40 (UTC-0700):
Look in /etc/udev/rules.d/ for a file
70-persistent-net.rules
It is probably there assigning the MAC address you want on eth0 to eth1. Likely it has two assignment lines. Just changing the assignment on the right address, a single character edit, and deleting the other line should be all you need to do before rebooting to find what you expected in the first place.
Adding a zero byte file
80-net-setup-link.rules
in rules.d/ might help to avoid future perplexity. See (near its bottom): http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface...
There are just two lines in 70-persistent-net.rules. Both have an ATTR(address) entry, but the ATTR(dev_id)=="0x0 and the ATTR(type)=="1". I have forgotten how to determine the MAC address. lspci shows a lot of info, but no mac address.
Among others: Shorter way: # ip a Longer way: hwinfo --network
lsattr on the troublesome machine has entries like ------./70-persistent-net.rules
That's in /etc/udev/rules.d/.
while on my functioning machine I get: ---------------- ./scripts ---------------- ./if-up.d ---------------- ./if-down.d ---------------- ./providers ---------------- ./routes ---------------- ./routes.YaST2save ---------------- ./ifroute-wlp11s0 ---------------- ./ifcfg.template ---------------- ./dhcp ---------------- ./ifcfg-enp9s0 ---------------- ./ifcfg-wlp11s0 ---------------- ./config ---------------- ./ifcfg-lo
That looks like from /etc/sysconfig/network/. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 28 Dec 2015 22:37, don fisher wrote:
On 12/28/2015 12:05 PM, Felix Miata wrote:
don fisher composed on 2015-12-28 11:40 (UTC-0700):
An unconfigured Ethernet device means that the system detect a hardware Ethernet device with a specific MAC address and does not find a matching configuration, ifcfg-ethX file. The udev system matches your hardware Ethernet device with the name eth1, but you do not have a file ifcfg-eth1. Same goes for your wireless device.
How does one fix this. I do not have eth1 any more. I deleted it and started over thinking all would be set up correctly. Why does the udev system want to match Ethernet MAC address to eth1, and not use eth0? I see no reference to a MAC address in the ifcfg file. I only have a single Ethernet adapter in the laptop. Also a single wireless adapter...
Look in /etc/udev/rules.d/ for a file
70-persistent-net.rules
It is probably there assigning the MAC address you want on eth0 to eth1. Likely it has two assignment lines. Just changing the assignment on the right address, a single character edit, and deleting the other line should be all you need to do before rebooting to find what you expected in the first place.
Adding a zero byte file
80-net-setup-link.rules
in rules.d/ might help to avoid future perplexity. See (near its bottom): http: //www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
There are just two lines in 70-persistent-net.rules. Both have an ATTR(address) entry, but the ATTR(dev_id)=="0x0 and the ATTR(type)=="1". I have forgotten how to determine the MAC address. lspci shows a lot of info, but no mac address.
Have you tried the command "hwinfo --network" as root? On my running machine it shows all the available info on my NICs, including the "HW Address:" which is the MAC address. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
don fisher -
Felix Miata -
Freek de Kruijf -
jdd -
Yamaban