I have to say, on the laptops which run KDE, using network manager is *great*. It has stabilized and works very well. Not being able to have more than one VPN is a problem, but it's a bit on the esoteric side. That said, wicked has caused me some real pain. On my non-GUI machines (servers, etc), wicked has been a real problem: - No support for if-up/if-down/if-services - Assumes all wireless devices will want to be clients, no ability to just configure the interface so I can run hostapd. - wicked uses the MTU from dhcp, and it can't be over-ridden (my provider chooses a poor MTU which - to date - I've been able to override) - *Weird* problems with routing table when interfaces come up or go down. I have captured at least *three* different routing tables, only one of which is correct, after an interface went down and came up. No amount of massaging seemed to work, and only a reboot seemed to help. Supremely irritating. On my servers, without access to traditional ifup/ifdown, I installed network manager and configured (most!) of the interfaces using the nmtui program (woo! a HUGE improvement in the utility of network manager). For the wireless, I had to figure out three things: 1. how to make network manager ignore interfaces (I chose to ignore by mac addr) 2. how to get udev to trigger a service when an interface becomes available 3. how to write a systemd service to come up/go down the the interface comes up/goes down 4. I had to remember to make sure to run SuSEfirewall2 via dispatcher.d. That this is not the default I consider a significant security hole! Now, if you can believe it, hostapd comes up automatically when the wireless interface (a usb device) appears, and goes away when the interface does. The weird routing problems are gone. I'm dismayed to see that systemd-networkd is not available as an alternative, but at least network manager works well enough. Perhaps using wicked "natively" (using the wicked-specific config files) would have been better, but the integration of wicked and/or the support for "legacy" if-up-style needs improvement. One has to ask if perhaps any efforts there might have been better spent in improving wicked *before* using it to replace an existing system. Summary: wicked *misconfigures* my routes, *mishandles* my wireless devices, and doesn't provide if-up compatibility for my needs. Network Manager gets close enough, configures all of my interfaces properly[1], routes properly, and allows me to override the MTU. [1] I can't seem to make network manager configure the wireless device *without* making it a wireless client or making it an AP. I *just want* to configure it with an IP address. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org