EDIT: adding ip route show info when doing it with YaST:
# ip route show
10.10.10.0/28 dev br1 proto kernel scope link src 10.10.10.2
100.111.0.0/16 dev wt0 proto kernel scope link src 100.111.120.148
192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.12
And when doing it with ip route add default via 192.168.0.1:
# ip route show
default via 192.168.0.1 dev br0
10.10.10.0/28 dev br1 proto kernel scope link src 10.10.10.2
100.111.0.0/16 dev wt0 proto kernel scope link src 100.111.120.148
192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.12
Yes, if you want to use Network Manager you have to switch. I do not known enough on Wicked to advise you on that.
This is what I have installed on tumbleweed that is NetworkManger specific:
> sudo zypper se --installed-only NetworkManager
S | Name | Summary | Type
---+----------------------------------+-----------------------------------------------------------------+--------
i | cockpit-networkmanager | Cockpit user interface for networking, using NetworkManager | package
i | kf6-networkmanager-qt | A Qt wrapper for NetworkManager DBus API | package
i | kf6-networkmanager-qt-imports | QML components for networkmanager-qt | package
i | libKF6NetworkManagerQt6 | A Qt wrapper for NetworkManager DBus API | package
i+ | NetworkManager | Standard Linux network configuration tool suite | package
i | NetworkManager-bluetooth | Bluetooth device plugin for NetworkManager | package
i | NetworkManager-branding-openSUSE | Default openSUSE branding for NetworkManager configuration file | package
i | NetworkManager-dns-dnsmasq | NetworkManager dispatcher script for DNS dnsmasq configuration | package
i | NetworkManager-openconnect | NetworkManager VPN support for OpenConnect | package
i | NetworkManager-openvpn | NetworkManager VPN support for OpenVPN | package
i | NetworkManager-pptp | NetworkManager VPN support for PPTP | package
i | NetworkManager-tui | NetworkManager curses-based UI | package
i | NetworkManager-wwan | Mobile broadband device plugin for NetworkManager | package
I am running KDE and the NM GUI is part of the KDE settings.
The first entry shows that another option is cockpit.
Interesting⌠I am using Cockpit to manage VMs. My question being: What about YaST DNS, DHCP server, etc modules? I use all those to manage my servers conveniently from one single place (not having to write several config files). Does Cockpit offer the same functionality?
ip route show
default via 192.168.0.254 dev br0
10.200.150.0/24 dev tun0 proto kernel scope link src 10.200.150.3
10.200.200.0/24 dev tun1 proto kernel scope link src 10.200.200.3
192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.2
192.168.10.0/24 dev virbr1 proto kernel scope link src 192.168.10.1 linkdown
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
Please be aware of the file â/etc/sysconfig/network/configâ âŚ
The following command should also point you to this configuration file:
> cat /etc/resolv.conf
If â/etc/resolv.confâ isnât a symbolic link pointing to â/run/netconfig/resolv.confâ then, there are some other issues weâll have to address âŚ
Almost everything you need to know about static routes, regardless of the network service â âwickedâ or âNetwork Managerâ or âsystemdâ â is contained in the following information:
should always list also any static IP routes setup on your system.
Please note that, if in â/etc/sysconfig/network/configâ the parameter âNETCONFIG_DNS_FORWARDERâ isnât set to the value âresolverâ when neither a BIND server nor a dnsmasq server is setup, then various strange DNS resolution effects will be seen on your system â
Could be a possible cause for the failed resolution of the address â8.8.8.8â to âdns.googleâ âŚ