Comment # 7 on bug 1157394 from Knut Alejandro Anderssen Gonz�lez

(In reply to Russell Sandish from comment #0)
> Going into the network configuration panel, and selecting wicked as the
> network manager, and clicking edit on a wifi interface, it correctly scans
> and finds the SSIDs available. When selecting an SSID, the form indicates
> that the access point is "ad hoc" and unencrypted. I set the encryption to
> WPA2-PSK, and no matter whether I set the mode to ad hoc or managed, when I
> click next, yast2 immediately returns its starting panel (normally it would
> spend a while thinking while it configures the network), and networking is
> not configured.

About returning directly to the interfaces list dialog, it is the expected
behavior. That is, before 'network-ng' there were a sequence which first
configured the interface address, hardware and general config, and then
specific wireless configuration.

Now, there is not an extra step for the specific wireless settings but it is in
its own tab. Apart of that, when choosing a different auth method the dialog is
changed dynamically showing fields or buttons depending on chosen option.

> 
> Wicked appears to be working correctly - I had saved some wicked
> configuration files, and I can load these and they work. But given wicked's
> XML configuration format doesn't appear to be documented, it has limited my
> ability to connect to new wifi connections that don't use the same
> encryption scheme.
> 
> Normally, I do a zypper dup every week, so I always running close the the
> latest Tumbleweed distro.
> 
> I first noticed this problem on 30th October, when I upgraded my network
> equipment at home, and attempted to connect to the new Wifi 4 AP (aka
> 802.11ac). I can also confirm that it did work on October 15th, so the
> problem could not have arisen much before that date.