Hello All, my problem is that I am unable to establish a wifi connection during the Leap 15 upgrade. In fact, I never had any success in getting a wifi connection to work on any of my previous openSUSE installs (14.2 and 14.3). I have always bypass the network connection error during my Leap installs, continue and finish the install and later establish a wifi connection on the newly installed OS. I'm am using a Dell XPS laptop, running both Win10 and Leap 14.3 and preferred not to do a new Leap install if I don't have to. I have customized my fstab to use shared partitions and I like my desktop the way it is. Prior to the Leap 15 upgrade, I recorded my wifi configuration from my current OS (Leap 14.3) and inputted the same values but for the life of me, I cannot get a wifi connection during the Leap 15 upgrade. My network card setting follows:

Device Type: wireless
Configuration Name: wlan0
Dynamic Address: DHCP ver 4 and 6
Activate Device: On Hotplug
Module Name: ath10k_pci
Operating Mode: Managed
Authentication Mode: WPA-PSK(ver 1 and 2), using passphrase

Scanning for network name works, I'm able to view my wifi connection so I don't think there is any hardware related problem. I researched a little bit on this problem and found some info that the DNS's for the Leap installs do not work correctly. Anyone who can substantiate this theory or help me fix this problem would be appreciated. I am also a slackware user and never had any issue with wifi connections using slackware. Thanks in advance for your help.

I would activate on system start or so, because its a PCI device......

@Wolfslacker, I faced problem with DNS whenever Leap 15 (or the previous 42.x releases) uses the default "wicked.service" for managing networks.

Essentially, the network would be available and can ping to an external IP, but wont resolve names. This also means that I cant update my system. Which is why I always switch to NetworkManager, and either use resolv.conf for DNS or edit NM connections and add my preferred DNS IPs from the networkmanager applet or from CLI.

However, I tested wicked.service just yesterday and it was able to resolve FQDNs thanks to the entries in resolv.conf. Maybe worth a shot.

Though I never had a problem with my TP-link PCI wireless card or USB dongles (which use Ralink/Ath9k Chipset). I admit that I never bothered to check if my wireless card is configured to be activate on boot, since it always worked out of the box. I also have a RJ45 wire connecting to my home router.

Also, just curious, do you mean Leap 42.3 when you say 14.3 ?

You can:
or delete /etc/resolv.conf (will be created once more on restart)
or try a Nameserver to /etc/resolv.conf such as:
But best are the first 2 ones.