No IP address picked up. NIC is up.

My Tumbleweed Plasma installation on my multimedia machine is not picking up an IP address.
ifconfig shows the onboard NIC is up.
If I run netconfig -f update there is no output.
If I remove and replace the Ethernet cable Network Manager senses it and tries to establish a connection.
I’ve rebooted the router, rebooted the switch rebooted the system several times. Was working fine up and after the Tumbleweed update before this latest one. (The big Python upgrade)
Right now this computer is as useful as a rock. Any ideas?

Hi
So is the output from the following valid?


cat /etc/resolv.conf
ip addr
ip route

OK. took a picture. For some reason it won’t let me insert an image.
https://photos.app.goo.gl/DLoYzGb33c462d1V9
Looks like it doesn’t know the route anymore?
How does that happen? Did a Tumbleweed update move something?

Looks like the BBS software does not pass Links properly any more.
As this machine is across the room and has a 52 minitor I have to look up at an angle to I’m trying to figure out how to get the output on to the forum.
Let me try and make a text file I can cut and paste and transfer on a USB stick.

And, ‘zypper dup’ was used?

Here is the output:

flamebait@Chair:~> cat /etc/resolv.conf
### /etc/resolv.conf is a symlink to /var/run/netconfig/resolv.conf
### autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
nameserver 8.8.8.8
nameserver 8.8.4.4
flamebait@Chair:~> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 24:be:05:09:70:1f brd ff:ff:ff:ff:ff:ff
flamebait@Chair:~> ip route
flamebait@Chair:~> netconfig update -f
Absolute path to 'netconfig' is '/sbin/netconfig', so running it may require superuser privileges (eg. root).
flamebait@Chair:~> sudo netconfig update -f
[sudo] password for root: 
flamebait@Chair:~> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 24:be:05:09:70:1f brd ff:ff:ff:ff:ff:ff

Yes. Always. It’s the only method to do a Tumbleweed update.

What does


sudo rcnetwork restart

do, Steven :slight_smile: ?

Solved.
Rooted around with the switches.
Network restored. There was no connection from that switch back to the master switch and router.
Seems a cable was dislodged.
Thanks for the replies and help.

… that would do it. LOL

Thanks for reporting back.