On Monday, 27 May 2019 11:14:39 ACST Mark Misulich wrote:
On Sun, 2019-05-26 at 22:16 +0200, Carlos E. R. wrote:
On 26/05/2019 19.05, Mark Misulich wrote:
Hi, I did a zypper dup from 15.0 to 15.1 this morning on my laptop. The process went without a hitch, but now that it is complete I can't connect to the internet anymore either with wifi or cable connection.
The first thing is to diagnose the problem, not to apply random solutions.
So, did you got an IP address?
As ifconfig will probably not be installed, try "ip addr", otherwise "ip link" or perhaps "ip netconf".
I used #curl ifconfig.me curl: (6) Could not resolve host: ifconfig.me
#curl api.ipify curl: (6) api.ipify
~ip addr <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 1c:2g:39:14:4s:2o brd ff:ff:ff:ff:ff:ff inet 192.147.1.1/24 brd 192.147.1.298 scope global noprefixroute dynamic wlan1 valid_lft 86277sec preferred_lft 86277sec inet6 fe80::85s6:15gg:41:4c7z/64 scope link noprefixroute valid_lft forever preferred_lft forever
Just shows the address of my wifi but not an ip address. However logging in to my wifi admin page, doesn't show the laptop connected to the wifi.
Then if you do have an IP, next see if you have a route, so "ip route" (all work as user).
#ip route #
Next is connectivity. Ping your router, then ping google at 8.8.8.8.
#ping 192.147.1.1 connect: Network is unreachable
Next is name solving, so ping google.com.
#ping www.gosgle.com ping: www.gosgle.com Name or service not known
(I did spell google correctly when I tried to ping, just trying to get rid of the hyperlink in this email).
Mark
As others have suggested, when troubleshooting networking, a methodical approach will always win over a scatter-gun approach. 1. Check for Layer 1 (physical layer) issues first: is the ethernet (wired) or wireless link up? If that isn't working, nothing else will. Check for configuration or device driver/kernel module/firmware issues. 2. Layer 2 - on most home networks, should be OK if Layer 1 is OK (unless VLANs are involved, which adds another layer of complexity). However, you'll need to know that ARP resolution is working - does your computer know the MAC address of the default gateway or next-hop router? 3. Layer 3 - check for an IP address in the correct (expected) subnet; if you don't have one, is DHCP working correctly, or are you using a static IP address? Check that the default gateway address is correct (it should be your router's IP address, again either assigned via DHCP or statically). Check that you can ping the default gateway; if not, is ARP resolution working (back to Layer 2). If all the above passes, then (and only then) check for external connectivity. If that still fails, repeat the above tests between the router and the ISP. Same approach, different devices. Always break it down to first principles. If the physical link is down, nothing works. If the physical link is up but Layer 2 (link layer) is not functioning correctly, nothing works above that etc. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ==============================================================