Tumbleweed installation fails to setup wired network

English Network/Internet
#1

On my SM workstation I have Leap and Tumblweed in dual boot setup. While wired network (eth1) on Leap works fine with a normal Network Manager icon on the top right Gnome desktop corner, it is just a “?” with no working connection on Tumbleweed.
This wired connection (eno1) dropdown menu contains profile 1 and profile 2 (no wire connected).

I have tried both Tumbleweed upgrade and new installation from DVD without any change. On another workstation Tumbleweed wired network connects just fine.
Suggestions to solve this issue?

#2

@terjejh what does the following show nmcli? Are you sharing $HOME?

#3

Not sharing $HOME.
Indeed TW root and home is on the common partition (while lp155 have separate partitions)

I thought first to attach the Network section from inxi -Fz:

Network:
  Device-1: Intel Ethernet I217-LM driver: e1000e
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel I210 Gigabit Network driver: igb
  IF: eno2 state: down mac: <filter>

and

nmcli
eno1: connected to Profile 1
    "Intel I217-LM"
    ethernet (e1000e), 0C:C4:7A:31:DF:5A, hw, mtu 1500
    ip4 default, ip6 default
    inet4 10.0.0.13/24
    route4 10.0.0.0/24 metric 100
    route4 default via 10.0.0.138 metric 20100
    inet6 2001:4649:a5e4:0:9fb8:638f:280f:853a/64
    inet6 2001:4649:a5e4:0:2872:2f36:a9d0:cbf1/128
    inet6 2001:4649:a5e4:0:ec6d:c01c:824f:6591/64
    inet6 fe80::56e4:ab8e:786c:b02d/64
    route6 fe80::/64 metric 1024
    route6 2001:4649:a5e4::/64 metric 100
    route6 default via fe80::763a:efff:fe0a:39b1 metric 20100
    route6 2001:4649:a5e4:0:2872:2f36:a9d0:cbf1/128 metric 100

lo: connected (externally) to lo
    "lo"
    loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
    inet4 127.0.0.1/8
    inet6 ::1/128
    route6 ::1/128 metric 256

eno2: unavailable
    "Intel I210"
    ethernet (igb), 0C:C4:7A:31:DF:5B, hw, mtu 1500

DNS configuration:
    servers: 148.122.16.252 148.122.164.252
    interface: eno1

    servers: 2001:4600:4:fff::252 2001:4600:4:1fff::252
    domains: home
    interface: eno1

In comparision I also attach nmcli from lp155 with working network/Internet on the same workstation:

eth1: connected to eth1
        "Intel I217-LM"
        ethernet (e1000e), 0C:C4:7A:31:DF:5A, hw, mtu 1500
        ip4 default, ip6 default
        inet4 10.0.0.13/24
        route4 10.0.0.0/24 metric 100
        route4 default via 10.0.0.138 metric 20100
        inet6 2001:4649:a5e4:0:7bfc:6cd2:8142:88f/64
        inet6 2001:4649:a5e4:0:a405:b0ef:6df5:a41/128
        inet6 2001:4649:a5e4:0:ec4:7aff:fe31:df5a/64
        inet6 fe80::ec4:7aff:fe31:df5a/64
        route6 fe80::/64 metric 1024
        route6 2001:4649:a5e4::/64 metric 100
        route6 2001:4649:a5e4:0:a405:b0ef:6df5:a41/128 metric 100
        route6 default via fe80::763a:efff:fe0a:39b1 metric 100

eth0: unavailable
        "Intel I210"
        ethernet (igb), 0C:C4:7A:31:DF:5B, hw, mtu 1500

lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
        servers: 148.122.16.252 148.122.164.252
        interface: eth1

        servers: 2001:4600:4:fff::252 2001:4600:4:1fff::252
        domains: home
        interface: eth1
#4

@terjejh So your actually connected, but NM decides you have limited connectivity. Do you have config files down in /etc/NetworkManager related to ‘connectivity’?

#5

Go to Yast, Network - switch to managed, then switch back to network manager and try again.

Are your network devices listed in Yast - Network?

#6

@ [malcolmlewis
I have no idea why tw give me limited connectivity on this hardware (while it works on another machine).

Apparantly tw does not create NetworkManager.conf (while lp15 does)

The available files and their content in /etc/NetworkManager are (notice the spaces in the file names!):

ls -1

Profile 1.nmconnection
Profile 2.nmconnection
Wired connection 1.nmconnection

cat Profile\ 1.nmconnection

[connection]
id=Profile 1
uuid=8c23f411-35cd-49e4-8cd2-a967ab54e37e
type=ethernet
interface-name=eno1
metered=2
timestamp=1688934998

[ethernet]

[ipv4]
method=auto

[ipv6]
addr-gen-mode=default
method=auto

[proxy]

cat Profile\ 2.nmconnection

[connection]
id=Profile 2
uuid=97bbe1bb-05b1-4129-a6d9-575cbd749cbb
type=ethernet
interface-name=eno1

[ethernet]
cloned-mac-address=stable
mac-address=0C:C4:7A:31:DF:5A

[ipv4]
method=auto

[ipv6]
addr-gen-mode=default
method=auto

[proxy]

cat Wired\ connection\ 1.nmconnection
[connection]
id=Wired connection 1
uuid=797abfed-54d5-3dfd-a995-73abcb7a32cc
type=ethernet
autoconnect-priority=-999
interface-name=eno2
metered=1

[ethernet]

[ipv4]
method=auto

[ipv6]
addr-gen-mode=default
method=auto

[proxy]

#7

@[qwert.zuiop
I’m not sure what “Go to Yast, Network - switch to managed” mean?

What YaST tell me is that Network is currently handled by NetworkManager
and further
Not configured eno1
Not configured eno2

#8

@terjejh I would delete them all and create a new profile name. Are you wanting dhcp or static?

#9

Go to Yast, Switch the network from NetworkManager to Yast Mode. Check your interfaces.
Configure DHCP Accept…

Then reopen Yast Network - Switch back to Network Manager.

Or do this in terminal, as Malcolm says.

#10

I did not succeed to get a working network or changing the “?” in the NM applet. Deleted all files as suggested /etc/NetworkManager/* and even tried to copy the content from the working lp155.

To shorten a longer story, it turned out that I by mistake had downloaded and installed a TW DVD i686 image (for the first time :grimacing: ). After re-downloading and a new re-installing the x86-64 image, the network was setup correctly and worked :ok_hand:

By the way, thank you both for the suggestions and help to troubleshoot this.

1 Like