as reported in the title, I did yesterday an upgrade in my desktop from Leap15.5 to 15.6.
The final result is that everything works but the communication no more.
At the reboot, I have my ethernet card, wired, reporting a “limited connectivity” and in fact I can’t connect to internet.
After tests and googling, I can post these results:
pinging locally, my router, is fine.
other PCs can ping my PC
pinging 8.8.8.8 is fine
“host google.com” works fine even if results differs from my laptop connected to the same network.
DESKTOP reports always the same address 192.178.57.46
LAPTOP reports varying adresses like 192.178.x.x, with a different address at every request
pinging google.com doesn’t work, it reports “name or service unknown”; on laptop is fine
no program is able to connect to internet
I dont know how to proceed now and what to check anymore.
Unless you have a specific need to use “wicked”, you will want to verify that the network is controlled by “NetworkManager” in yast. That is the easiest approach I can think of.
On Leap, you can choose either. If you don’t have a specific reason to use “wicked”, “NetworkManager” will probably be easier, as the network can be directly managed from gnome or kde.
Open yast and click on on “Network Setting”, and the rest should be obvious from there. In the first tab, called “Global Options”, there is a “Network Setup Method” that allows you to choose between “wicked” and “Network Manager” or “Network Manager” and “Network Services Disabled”.
Hy oxwrongagain, yes I know about chnaging network managing service.
In fact by default was Network Manager, and I tried changing it for the Wicked, but even here I had no luck.
Just to add some additional info, I even tried to switch off the firewall, thinking that if system cmds like HOST is able to identify somehow an address it can be possible that a port is remained closed when firewall is active.
I’ve tried to use the command “nc” to identify the ports that are open but with the cmd line nc -z -v localhost 1-400, I have the response nc: getaddrinfo for host "localhost" port 1: Name or service not known .
Doing the same cmd using an ip address I have back some results, but I just don’t know which direction I supposed to use; my PC ip address?
Ah… the DHCP service is working and my card receive the IP from the router.
I don’t know… it seems something broken inside, something like DNS requests are not handed over to the main service, Network Manager or Wicked.
I am not certain that “dhcpv6-client” is needed, but it couldn’t hurt.
First, make sure you have configured the network to use NetworkManager in yast.
You can verify that it is running with “systemctl status NetworkManger” and restart it with “systemctl restart NetworkManager”.
DNS info is in /etc/resolv.conf, which is just a link:
root@orca# ll /etc/resolv.conf
lrwxrwxrwx 1 root root 26 Jun 13 21:50 /etc/resolv.conf -> /run/netconfig/resolv.conf
root@orca# cat /etc/resolv.conf
### /etc/resolv.conf is a symlink to /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.
search attlocal.net
nameserver 192.168.1.254
nameserver 2600:1702:3d10:2aa0::1
Perhaps there is unneeded stuff in /etc/sysconfig/network/config from your previous install.
The contents of mine (so you have an example of something that is working)
Hy again @oxwrongagain, I look after your infos and all seems to me, working normally.
Comparing youe settings with mines there are no differences, and for the firewall the services I’ve included are more than yours and are a copy of what appears in my laptop, sothey should be working.
I already restarted several times the network manager service with no results.
I will try to perform a rescue system somehow and finally if nothing works I will format the main disk an reinstall Leap15.6.
Thank you very much for your help
Sorry for the late replay, I was abroad for work.
Soon after the last reply, I reinstalled Leap 15.6, and everything went smooth.
Anyway, today after I changed, or better said, messed up with the settings of SAMBA, I again experienced the “Limited connectivity” error.
And as you correctly suggesting this file /etc/nsswitch.conf was the guilty piece of sw.
Considering I didn’t exactly know what to do, I limited myself to rename this file and renaming the /etc/nsswitch.confbak file as /etc/nsswitch.conf
Once rebooted, the communication started normally.
Thank you everybody for your help.
