Internet Connection not working

lolone · January 10, 2020, 11:43am

I’ve just installed openSUSE Leap 15 for the first time. Unfortunately I’m unable to get my internet connection working.

I was searching around in the forums and it seems like other people have the exact same problem and no solution was reached there

What I’ve done:

connected an ethernet cable, set the connection to Dynamic address

deleted /etc/resolv.conf and rebooted
when that didn’t work, tried

netconfig update -f

to no avail.

some recommended comments and their outputs:


ping -c1 forums.opensuse.org
ping: forums.opensuse.org: Name or service not known


ping -c1 192.168.0.1
connect: Network is unreachable


ip add
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
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:d8:61:a2:7e:f7 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether d0:37:45:41:a5:13 brd ff:ff:ff:ff:ff:ff


ip route
 ->gives me no output

The computer is a self built desktop, AMD Ryzen 5 processor and MSI motherboard, so not exactly exotic hardware. In Ubuntu everything worked out of the box.

Any help is appreciated.

hcvv · January 10, 2020, 12:08pm

The ip add shows that there is no NIC configured with an IP address. Thus there is not only no connection to the Internet, there is no connection to your LAN to begin with.

Hwo did you configure the network?
Did you choose for Wicked or for NetworkManager?
You say “set the connection to Dynamic address”, I assume you mean you want to use DHCP, but where and how did you set it?

Remember that we can not look over your shoulder to see what you do, thus you have to explain everything.

lolone · January 10, 2020, 12:21pm

Thanks for the quick reply.

To be honest I have no idea what most of those terms mean. Searching for “wicked” or “network manager” in the application launcher gives me nothing.

I used Yast - system - network settings, pressed edit on the wired connection, set that to dynamic address DCHP and clicked next, as someone recommended on this forum to a user with a similar problem.

During the install I tried to connect the wifi, but it was confusing layout and it didn’t work, so I figured I could just skip it and do it later in 2 clicks from the desktop, as that’s what it was in Ubuntu.

knurpht · January 10, 2020, 12:32pm

Please show


sudo lspci
sudo lsusb

hcvv · January 10, 2020, 12:33pm

OK, usimg YaST Network Settings and then editing the eth0 device makes this using Wicked (you will see somewhere there a choice between Wicked and Network Manager, when choosing NM, you can not do much with YaST anymore, the fact that you configured using DHCP in YaST means that you did not choose NM).

Now when you use DHCP, there should be a functioning DHCP server in your LAN. Normaly that is the router that connects your LAN to the internet. And that router is often given to you by your Internet Provider. Are you sure you have such a router, that it is functioning (e.g. by the fact that other systems on the LAN can use it), and that the cable connection to it is OK?

lolone · January 10, 2020, 1:41pm

sudo lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15d0
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 15d1
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15d3
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15db
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15dc
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15e8
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15e9
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ea
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15eb
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ec
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ed
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ee
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ef
12:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43d5 (rev 01)
12:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43c8 (rev 01)
12:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43c6 (rev 01)
20:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43c7 (rev 01)
20:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43c7 (rev 01)
20:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43c7 (rev 01)
20:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43c7 (rev 01)
20:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43c7 (rev 01)
20:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43c7 (rev 01)
25:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
26:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192EE PCIe Wireless Network Adapter
29:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 15d8 (rev c8)
29:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 15de
29:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Device 15df
29:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15e0
29:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15e1
29:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Device 15e3
2a:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 61)

sudo lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical Mouse
Bus 001 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Now when you use DHCP, there should be a functioning DHCP server in your LAN. Normaly that is the router that connects your LAN to the internet. And that router is often given to you by your Internet Provider. Are you sure you have such a router, that it is functioning (e.g. by the fact that other systems on the LAN can use it), and that the cable connection to it is OK?

I made a reboot in between, tried switching from wicked to networkmanager and back, ran the commands Knurpht recommended. One of them must have changed something. I get

ping -c1 forums.opensuse.org
PING forums.opensuse.org (130.57.66.6) 56(84) bytes of data.
64 bytes from 130.57.66.6 (130.57.66.6): icmp_seq=1 ttl=46 time=161 ms

--- forums.opensuse.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 161.420/161.420/161.420/0.000 ms

ping -c1 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.330 ms

--- 192.168.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.330/0.330/0.330/0.000 ms

ip route
default via 192.168.0.1 dev eth0 proto dhcp 
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.102

ip add
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
    inet6 ::1/128 scope host 
       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 00:d8:61:a2:7e:f7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.102/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::2d8:61ff:fea2:7ef7/64 scope link 
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether d0:37:45:41:a5:13 brd ff:ff:ff:ff:ff:ff
blacktip@linux-ymtz:/etc> ip route
default via 192.168.0.1 dev eth0 proto dhcp 
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.102

everything is working, at least with the eternet cable. I’ve done the updates, rebooted, wired still works, half of the problem solved!

Tried the same network settings program for the wireless, selected the network and entered the key. When I remove the ethernet cable it disconnects again. I get

ping -c1 forums.opensuse.org
ping: forums.opensuse.org: Temporary failure in name resolution

ping -c1 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.102 icmp_seq=1 Destination Host Unreachable

--- 192.168.0.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

ip route
default via 192.168.0.1 dev eth0 proto dhcp linkdown 
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.102 linkdown

ip add
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
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 00:d8:61:a2:7e:f7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.102/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::2d8:61ff:fea2:7ef7/64 scope link 
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether d0:37:45:41:a5:13 brd ff:ff:ff:ff:ff:ff

hcvv · January 10, 2020, 2:13pm

I do not think one of those commands Knurpht asked for did anything but making the listings.

But indeed now it functions. Congratulations and enjoy using openSUSE.

eng-int · January 10, 2020, 2:22pm

You seem to have an RTL8192EE wireless card.
According to:
https://software.opensuse.org/package/rtl8192ee-firmware?search_term=RTL8192EE
there is no official Leap-15.1 driver for this card, but a well-known forum wireless expert has compiled a driver package that you can install by clicking on:
https://software.opensuse.org/ymp/home:Sauerland/openSUSE_Leap_15.1/rtl8192ee-firmware.ymp?base=openSUSE%3ALeap%3A15.1&query=rtl8192ee-firmware

lolone · January 10, 2020, 3:07pm

I’ve installed the package and rebooted, but it still doesn’t work. When removing the cable it gives me the exact same outputs I had earlier when the wired connection didn’t work


ping -c1 forums.opensuse.org
ping: forums.opensuse.org: Name or service not known


ping -c1 192.168.0.1
connect: Network is unreachable


ip add
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
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:d8:61:a2:7e:f7 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether d0:37:45:41:a5:13 brd ff:ff:ff:ff:ff:ff


ip route
 ->gives me no output

Also find it weird that there are no drivers for it, since it worked on Ubuntu, and when I ordered it it said in the description that it was compatible with linux kernel 2.6, and even has a linux support logo on the box.:dont-know:

hcvv · January 10, 2020, 3:30pm

That is logical. You only configured your cable NIC, not your wireless. And you never told you want to use the wireless device. You only talked about a cable connection, so I though that now it works and case closed.

We do not know much about your goal. What do you want with the system? Is it a computer room one, a desktop, or another one that always sits in the same place and uses the same network?

Or is it a walk around system, e.g. a laptop or notebook that connects to networks that are avaialbel in the place where it happens to be?

In the second case, you should use NetworkManager.

lolone · January 10, 2020, 3:46pm

It’s a desktop, it’s meant to mainly connect to my wifi. Cable connection is inconvenient, means I will have a cable cross the room at all times, which I don’t want.

I tried configuring the wifi the same way, it scanned the networks and I got to enter the security key. So what else do I have to do?

hcvv · January 10, 2020, 4:55pm

Yes, configure with YaST like the cable. Enter the SSID and the password/string, whatever. Should just work.

lolone · January 10, 2020, 5:36pm

I’ve been trying that, trying all different Authentication Modes, currently trying the WPA and it seems a little better than higher up but I still just can’t get it to work. I’m sure I’m using the right key and the router is on, fwiw:)


ping -c1 forums.opensuse.org
ping: forums.opensuse.org: Temporary failure in name resolution

ping -c1 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.102 icmp_seq=1 Destination Host Unreachable

--- 192.168.0.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

ip add
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
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 00:d8:61:a2:7e:f7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.102/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::2d8:61ff:fea2:7ef7/64 scope link 
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether d0:37:45:41:a5:13 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.103/24 brd 192.168.0.255 scope global wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::d237:45ff:fe41:a513/64 scope link 
       valid_lft forever preferred_lft forever

ip route
default via 192.168.0.1 dev eth0 proto dhcp linkdown 
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.102 linkdown 
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.103

hcvv · January 10, 2020, 6:23pm

You should remove the cable when you try out the Wifi.

BTW you show those test statements in the wrong way. First

ip addr

When that shows a correct configured NIC, and only then, you go for

ping -c1 192.168.0.1

When that is OK, and only then, you do the

ip route

When that shows a defualt rout to your router, and only then, you chek if you can go out tothe internet with

ping -c1 130.57.66.6

When you can connect there, and only then, you then check DNS with

ping -c1 forums.opensuse.org

It is pretty useless to do e.g. ping to the forums when you do not even have a configured NIC. So stop after you detect something that not works, report here and we will try to help you.

eng-int · January 10, 2020, 10:06pm

You can configure wlan0 with eth0 connected, only disconnect the cable for testing. Restart and check the network protocols with:

rayh@yoga3:~> sudo systemctl restart network
 
rayh@yoga3:~> sudo systemctl status network 
● wicked.service - wicked managed network interfaces
   Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled)
   Active: active (exited) since Fri 2020-01-10 20:22:57 GMT; 25s ago
  Process: 8755 ExecStop=/usr/sbin/wicked --systemd ifdown all (code=exited, status=0/SUCCESS)
  Process: 8843 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS)
 Main PID: 8843 (code=exited, status=0/SUCCESS)

Jan 10 20:22:27 yoga3 systemd[1]: Stopped wicked managed network interfaces.
Jan 10 20:22:27 yoga3 systemd[1]: Starting wicked managed network interfaces...
Jan 10 20:22:57 yoga3 wicked[8843]: lo              up
Jan 10 20:22:57 yoga3 wicked[8843]: wlan0           up
Jan 10 20:22:57 yoga3 wicked[8843]: eth2            no-device
Jan 10 20:22:57 yoga3 systemd[1]: Started wicked managed network interfaces.
rayh@yoga3:~>

The first thing is to establish whether your wlan0 can see your wireless network (SSID)
YaST > System > Network Settings
Global Options > Network Setup Method = Wicked Service
Overview [select wlan0] Edit
Address = Dynamic Address > Next
Wireless Device Settings
Operating Mode = Managed, [select] Scan Network
[check that your router’s SSID can be selected from ] Network Name (ESSID)

Only if SSID selection is successful;
select the Authentication Mode – probably WPA-PSK (WPA version 1 or 2)
Key Input Type = *Passphrase, Encryption Key = *your WiFi password
> Next > OK

The wireless settings can be checked (and edited) in */etc/sysconfig/network/ifcfg-wlan0

**