Bug ID 995167
Summary WiFi configuration with WPA2-PSK for a hidden network won't be accepted during installation
Classification openSUSE
Product openSUSE Distribution
Version Leap 42.2
Hardware All
OS SUSE Other
Status NEW
Severity Normal
Priority P5 - None
Component Installation
Assignee yast2-maintainers@suse.de
Reporter ada.lovelace@gmx.de
QA Contact jsrain@suse.com
Found By ---
Blocker ---

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:48.0) Gecko/20100101
Firefox/48.0
Build Identifier: 

I use a hidden network with WPA2-PSK at home.
After testing the fix for bug 992516 on openSUSE Tumbleweed, the problem with
the hidden network exists for a longer time. The network configuration won't be
accepted or the network won't be found.
It seems it needs something to choose like after the installation in the WiFi
configuration for "hidden networks". 
workaround at the moment: Installation without adding repositories and adding
the WiFi after the installation with choosing "hidden network" (verstecktes
Netzwerk)

The problem will be that "hidden networks" (security) won`t be supported during
installations. 


Reproducible: Always

Steps to Reproduce:
1. configure your WiFi with WPA2-PSK and as a hidden network (not public to
find)
2. configure the wlan interface for WPA2-PSK with a password during the
installation
3. The WiFi can't be found. (no error message)
4. Online repositories can't be used.
5. Looking after the network configuration again (it is configured).
6. installation without repositories
7. configuration of the network interface after the openSUSE installation
successfully

(openSUSE Tumbleweed was used: reason bug 992516)
Actual Results:  
The WiFi configuration with WPA2-PSK with a hidden network (verstecktes
Netzwerk) won't be accepted during the installation of openSUSE Leap/
Tumbleweed.

The WiFi works after a configuration after the installation.

Expected Results:  
You can choose every WiFi (unimportant whether public or hidden network) during
the installation. 

You can't reproduce it on Leap at the moment, because another (fixed) network
configuration bug exists there at the moment. Use Tumbleweed for that!


You are receiving this mail because: