Wicked really is well-named.

Can someone please suggest how I can get “wicked” to work on a laptop
to set up a wireless connection? I’ve used the same settings as with
“ifup” but have had no success. I’ve also tried umpteen variations with
the settings and also gotten nowhere.

I prefer to use “ifup” as my laptop almost always uses the same
wireless connection so Network Manager is not so convenient although it
does at least work.


Graham P Davis, Bracknell, Berks.
openSUSE 13.1 (64-bit); KDE 4.13.3; AMD Phenom II X2 550 Processor;
Kernel: 3.11.10; Video: nVidia GeForce 210 (using nVidia driver);
Sound: ATI SBx00 Azalia (Intel HDA)

I don’t have factory on a laptop.

I tried the next best thing. I plugged in a WiFi USB card.

I configured with Yast (using “wicked”). It seemed to go well, and it now has an IP address.

After plugging in the device, I started Yast Network Settings.

It showed the device as unconfigured. I clicked “Edit”. It told me that the device needs firmware, and to click “Continue” if I had already installed the firmware (I had). I clicked “Continue”.

It defaulted to a hard wired IP. I switched that to DHCP for IPv4. I clicked Next.

That gave me the wireless settings screen. I told it to search for SSID, and it found the right one. I set security to WPA-PSK, and entered the passphrase. I clicked Next and/or Finish a couple of times. It looks as if everything is working. I am able to ping and connect from another computer.

I have not tried rebooting with the WiFi card plugged in. And I also have ethernet, so my tests don’t say anything about routing.

I just did this on my laptop.

As background, I installed from the KDE live snapshot 20140820. The install mostly worked. There’s a nasty error message on first reboot, but clicking “Quit” gave me a working system. I had to manually enable the firewall.

WiFi worked with NetworkManager (sort of worked).

I switched to “wicked”.

After my first attempt to configure WiFi, I had no network.

I then ran: “systemctl restart network”

I still had no network.

Back into Yast network settings, clicked edit on the WiFi device.
I went to the “General” tab. I switched “Activate Device” from “Boot time” to “On cable Connect”.

After hitting Next, etc, I had a WiFi connection.

Rebooted. I had a WiFi connection.

Problem: When I first boot the system, I have an IPv4 address, but no IPv6 (other than the link-local address). This happens on most boots, whether using NetworkManager or wicked.

With NetworkManager, if I disconnect, then reconnect, I get IPv6 addresses. With wicked, “systemctl restart network” gets me IPv6 addresses. I did not have this problem with opensuse 13.1.

Another note: Running the live KDE from USB, I do get IPv6 addresses for WiFi on boot. My best guess is that there is some strange timing issue involved here and the slower booting with the live media is why it works.

On Tue, 26 Aug 2014 13:56:01 GMT
nrickert <nrickert@no-mx.forums.opensuse.org> wrote:

> Back into Yast network settings, clicked edit on the WiFi device.
> I went to the “General” tab. I switched “Activate Device” from “Boot
> time” to “On cable Connect”.
>
> After hitting Next, etc, I had a WiFi connection.
>
> Rebooted. I had a WiFi connection.

Yes, I usually use that with ifup but it didn’t work with Wicked. Also
tried “on hotplug” - which also works with ifup - but that was also a
complete failure.

Tried my usual method of defining an IP address and then changed to
DHCP when that failed but it made no difference.


Graham P Davis, Bracknell, Berks.
openSUSE 13.1 (64-bit); KDE 4.13.3; AMD Phenom II X2 550 Processor;
Kernel: 3.11.10; Video: nVidia GeForce 210 (using nVidia driver);
Sound: ATI SBx00 Azalia (Intel HDA)

Probably not relevant, but I did set the system to use DHCP only for IPv4 (rather than the default of both 4 and 6).

disabling ipv6 helped a lot here. instead of 15 seconds wicked now needs only 5 seconds of the boot process, seen in systemd-analyze blame.

this is on factory. 13.1 had no such problems and needed only 1 second.

thx

I agree that this thread is well-named. I’ve tried everything to get my network running with wicked and nothing has worked. It always says the state of my wireless is DOWN. I’ve submitted a bug report, bug#893678. and attached logs but no solution is yet to be found. One of my logs was interpreted by the asignee that NM and wicked were running at the same time. Yet the ‘show Id’ command always comes up ‘Id=wicked.service.’

Really strange that wicked is working for some but not for me and the OP.

On Fri, 19 Sep 2014 23:46:01 GMT
pilotgi <pilotgi@no-mx.forums.opensuse.org> wrote:

>
> I agree that this thread is well-named. I’ve tried everything to get
> my network running with wicked and nothing has worked. It always says
> the state of my wireless is DOWN. I’ve submitted a bug report,
> bug#893678. and attached logs but no solution is yet to be found. One
> of my logs was interpreted by the asignee that NM and wicked were
> running at the same time. Yet the ‘show Id’ command always comes up
> ‘Id=wicked.service.’
>
> Really strange that wicked is working for some but not for me and the
> OP.
>

I’ve also commented on the factory mailing list about an apparent lack
of any documentation for this new system. All I’ve learnt so far from
that is that “Wicked” has nothing to do with “WICD”, pronounced
“wicked”.

I’ve added my two-pennorth to your bug report.


Graham P Davis, Bracknell, Berks.
openSUSE 13.2-m0 (64-bit); KDE 4.14.0; AMD Phenom II X2 550 Processor;
Kernel: 3.16.1; Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA)

Lol! Read http://en.wikipedia.org/wiki/Wicked_problem

And of course wicked is part of systemd. Says it all IMHO.

Written with a blink in my eye ;).

regards

Where have you got this nonsense from?

It was meant as a joke but:

Or did I miss something? Was I misunderstand as usual (will not be the first time)?

regards

I’m not able to make wicked work on my desktop, is it possible to install the old traditional ifup method?

I don’t think so, though I could be wrong.

If you have an explicit problem, report it as a bug. That’s how things get fixed.

In the meantime, if “NetworkManager” works for you, then use that.

Not officially. It may be possible to install package from 13.1 (it is a bunch of shell scripts after all) and disable wicked services but it is unlikely you will be able to use yast then.