No connection using wicked service

English Network/Internet
#1

I have problem with the KDE network manager widget that prompts for root password on startup and about every 2 secs when I open the widget up.

I am switching to wicked service. But after setting it up using Yast-Network settings, it always shows wireless adapter (not connected).

And pinging gateway says “network unreachable”.

So far I have committed the following command and reboot, but it is still the same:

systemctl enable --force wicked
systemctl start wickedd.service
systemctl start wicked.service           
systemctl start network.service

edit: p.s. For more info, the “systemctl status wicked” shows the service is loaded and enabled, but the active shows “active (exited) since…”

#2

Can you start by sharing your working /etc/sysconfig/network/ifcfg-*** file (eg ifcfg-wlan0)?

What happens if you try to bring the interface (eg wlan0) up manually?

sudo ifup wlan0
#3

Thank you. So it is this magic command that works. Didn’t know there’s this step to use wifi.

I however encounter the other problem that I can only connect to my virtual wireless 10.0.0.1 network but not my main 192.168.1.1 network that leads to internet. I can ping any machine in 10.0.0.* but not 192.168.1.*.

Do I have to setup routing in Yast-network service too?

#4

The ifup command is as old as the hills. It’s used to bring up (or down) a pre-configured network interface. Refer to the man page for details. However, depending on your interface configuration, it can be made to start at boot (which I assume is what you expected). That’s why I asked you to share your current working configuration.

I however encounter the other problem that I can only connect to my virtual wireless 10.0.0.1 network but not my main 192.168.1.1 network that leads to internet. I can ping any machine in 10.0.0.* but not 192.168.1.*.

Do I have to setup routing in Yast-network service too?

This is the first time that you mention the existence of any other network that you wish to reach. You should share your network topology. Always provide as much definitive detail as possible to help eliminate guessing.

#5

The reason why wicked is not recommended for wireless networks is that it can work with only one network configuration at a time, if you configure a new network connection then the old one is lost…

When you used YaST > Network Settings to switch from NM to Wicked and found the wireless network adapter unavailable, my guess is that was because you hadn’t yet configured the adapter. Configured to use Wicked, you should then “Edit…” the wireless network adapter (I assume it’s listed) as a DHCP client (assuming that’s what you want). When you do this, YaST should run a small test to verify your settings work. A reboot may then be necessary to be certain your settings are locked in.

But, as I mentioned above… Unless your machine always stays in one place connecting to the same AP, wicked isn’t likely the preferred way to set up your wireless networking.

TSU

#6

I don’t think this was the case. The configuration had been made, otherwise the ifup command would not have worked. :wink:

#7

I kinda “fixed” the nm applet issue by creating a new user to start fresh. Yeah I had the adapter edited in wicked but somehow it wasn’t turned on. Thanks for pointing out that wicked is not ideal for wireless connection. I’m even happier that I’ve solved the nm applet issue.

#8

I don’t think that was quite what was meant. Either can be used to create a network connection. NetworkManager is better for those who frequently connect to different network environments as it permits multiple connection profiles to be defined.

#9

Maybe superfluous, but I want to stress that what the others say about wicked vs. nm is

  • NOT about cable vs. Wifi;
  • NOT about desktop vs. laptop;
  • it is about fixed IP address as mostly used by computer-room/office-desktop/allways-used-on-the same-wifi-network systems vs. systems that are walked around and thus use different network (home/airport/pub/office/hotel/…) all the time.

In the “fixed” case (which is not the same as a “fixed” IP address, but that goes very well with it) it is the system manager (root) that configures all and the user has no need to worry or interfere with the network configuration.

In the “walk around” case, there must be user interference because only the user (let us hope there is only one realy using the system at such moments in time) can make decisions on e.g. which of the available Wifi APs to use when on a specific geographical place. This situation, where the end-user must have influence on the network configuration is where NM was designed for (it is in fact a client-server solution where the server runs with root as owner because the network can only be handled by a root owned process).