I’m a long time OpenSuse user (since release 9.0). I recently decided to update my old 13.1 install (worked OK for 4+ years) – I have to use Tumbleweed because I’ve got a 32-bit system.
Yesterday (Monday, October 2) I upgraded my previously installed Tumbleweed system using the .iso network installation disk (I was having boot-up trouble with the Plasma 5 desktop). The upgrade went smoothly, I booted from the hard disk (once) with the DVD still in the drive, and everything worked fine for about 24 hours.
This morning I figured I’d reboot the system and put the DVD away. Boy, was that a mistake! >:( The system appeared to boot just fine. The Plasma 5 desktop started without any trouble. I fired up Firefox, and it said “No Internet Connection”. So I logged into my NetGear router at 192.168.1.1, and it said my internet connection is just fine. (I have three computers at home – my Linux machine is hardwired to 192.168.1.4. I’m writing this post from my Windows machine, which uses a wi-fi connection.)
Next I tried opening KMAIL; it also says “No Internet connection”. Then I ran KINFOCENTER, and looked at Network Connections. It said the Broadcast connection enp1s8 at ip address 192.168.1.4 was up and running.
I figured it might be a random hiccup, so I booted up again – same result.
Since I didn’t know what else to do, I booted from the .iso DVD (network install version) again to retry the upgrade that worked yesterday. That’s still running as I write this, but I did watch it long enough to see that the network connection at 192:168.1.4:24 was working; it had contacted opensuse.org and was downloading the “installation systems” when I left so I could post this query.
Any help would be greatly appreciated. Hopefully I’ll have Linux running in about an hour, and this time I won’t reboot until either (a) the problem is resolved, or (b) I have to. Thanks!
While the “No internet connection” tells us something, we really need to
know the networking information specifics that you can either get form
Network Manager, or else from the CLI. Sine the CLI is easier to
copy/paste than screenshots, please run he following commands and post
back the results, particularly when the system is NOT working, but even
when it is if you would like (for comparison):
ip -s link
ip a
ip r
grep -v -e '^#' /etc/resolv.conf
ping -c 4 192.168.1.1 #replace 192.168.1.1 with your router IP address
ping -c 4 8.8.8.8
These commands show link/NIC information, IP information, route/gateway
information, show DNS settings, and then do some layer three (3) network
tests using ICMP to a couple places that usually work nicely for any system.
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
OK, I guess I need to enter a sequence of commands at the Command Line prompt (“CLI”). I’ll do it and get back to you shortly. It may take a while since my LINUX machine is still offline; upgrading didn’t fix my problem.
Thank you very much. I’d click on the star, but I’m not sure where to find it. I don’t care if others read my posts, so there’s no need for a private message. dcb
Well now my graphical interface won’t boot (boot dies after initiating X11 and before displaying the “splash” screen or the Plasma 5 desktop). I did boot the “rescue” system and log in manually, but since I don’t know LINUX commands well enough to print the screen output, getting the results copied to this forum is pretty difficult. Here is the one result I did obtain.
Oh – I found the star (lower left corner of the message box) and I gave you a bump up. If I ever get my boot problems resolved, and if the internet problem persists, I’ll return to this topic. Thanks again for trying to help me out. IMHO, Tumbleweed is turning into a real pain.
I haven’t done any manual configuration of much of anything besides the GRUB2 bootloader, where I added a parameter “NOMODESET”, which helped (for a while) with the GUI interface (aka Plasma 5 desktop). That, and some stuff that affected the scroll bars in application programs, plus some “energy saver” settings to get the system to turn my monitor off after long periods of inactivity. Nothing to do with networking, so far as I can tell.
I’m not entirely certain what you mean by “your router’s internal IP address”. I can log into the router from a browser – that address is 192.168.1.1. The internet connection is currently configured to get a dynamic IP address from my ISP. That address (my current IP address from the outside world’s point of view) is 69.166.92.223 at the moment. The “Gateway IP address” is currently set to 69.166.92.193 – I’m not sure what that one is – something to do with dynamic reassignment of my IP address, I suppose.
So I was finally frustrated enough that I re-installed Tumbleweed from the beginning (that part is getting old). Anyway, my system is up and running just fine at the moment. Here’s the output you requested.
david@localhost:~> ip -s link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
RX: bytes packets errors dropped overrun mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
2: enp1s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 00:07:e9:42:94:14 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
844507 2414 0 6 0 0
TX: bytes packets errors dropped carrier collsns
286314 2086 0 0 0 0
david@localhost:~> ip a
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: enp1s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:07:e9:42:94:14 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.3/24 brd 192.168.1.255 scope global enp1s8
valid_lft forever preferred_lft forever
inet6 fe80::207:e9ff:fe42:9414/64 scope link
valid_lft forever preferred_lft forever
david@localhost:~> ip r
default via 192.168.1.1 dev enp1s8 proto dhcp
192.168.1.0/24 dev enp1s8 proto kernel scope link src 192.168.1.3
david@localhost:~> grep -v -e '^#' /etc/resolv.conf
nameserver 192.168.1.1
david@localhost:~> ping -c 4 69.166.92.223
PING 69.166.92.223 (69.166.92.223) 56(84) bytes of data.
64 bytes from 69.166.92.223: icmp_seq=1 ttl=64 time=0.313 ms
64 bytes from 69.166.92.223: icmp_seq=2 ttl=64 time=0.238 ms
64 bytes from 69.166.92.223: icmp_seq=3 ttl=64 time=0.243 ms
64 bytes from 69.166.92.223: icmp_seq=4 ttl=64 time=0.246 ms
--- 69.166.92.223 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3066ms
rtt min/avg/max/mdev = 0.238/0.260/0.313/0.030 ms
david@localhost:~> ping -c 4 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=11.4 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=11.4 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=11.9 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=56 time=10.9 ms
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 10.907/11.452/11.956/0.379 ms
If the problem recurs, I’ll be back. For now, I’m as happy as a clam.
Well, my internet is working OK right now – see my post to “ab” right below yours. But I can use the practice with posting in the forum, etc. Here you go.
ping -c1 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.325 ms
--- 192.168.1.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.325/0.325/0.325/0.000 ms
ping -c3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=10.9 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=11.0 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=11.6 ms
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 10.929/11.214/11.696/0.353 ms
ping -c3 google.com
PING google.com (172.217.2.238) 56(84) bytes of data.
64 bytes from dfw28s01-in-f14.1e100.net (172.217.2.238): icmp_seq=1 ttl=53 time=15.7 ms
64 bytes from dfw28s01-in-f14.1e100.net (172.217.2.238): icmp_seq=2 ttl=53 time=15.3 ms
64 bytes from dfw28s01-in-f14.1e100.net (172.217.2.238): icmp_seq=3 ttl=53 time=15.9 ms
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 15.332/15.687/15.970/0.284 ms