YaST not saving or even applying static ip routes

(Just showing the relevant interfaces)

# ip add
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br1 state UP group default qlen 1000
    link/ether 00:25:00:ee:6b:53 brd ff:ff:ff:ff:ff:ff
    altname enp10s0
    inet6 fe80::225:ff:feee:6b53/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000
    link/ether 00:25:00:ee:41:52 brd ff:ff:ff:ff:ff:ff
    altname enp11s0
4: br1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:25:00:ee:6b:53 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.2/28 brd 10.10.10.15 scope global br1
       valid_lft forever preferred_lft forever
    inet6 fe80::225:ff:feee:6b53/64 scope link 
       valid_lft forever preferred_lft forever
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:25:00:ee:41:52 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.12/24 brd 192.168.0.255 scope global br0
       valid_lft forever preferred_lft forever
    inet6 fe80::225:ff:feee:4152/64 scope link 
       valid_lft forever preferred_lft forever

br0 bonded to eth1 and thus, br1 to eth0.

I have created the following ip default route on YaST:

Yet

# ping 8.8.8.8
ping: connect: Network is unreachable

# cat routes.YaST2save shows nothing, so does # cat routes (/etc/sysconfig/network)

Yet when I do:

# ip route add default via 192.168.0.1
apple-srv:/etc/sysconfig/network # ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=249 time=15.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=249 time=13.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=249 time=15.5 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=249 time=13.9 ms
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 13.775/14.574/15.535/0.745 ms

I was under the impression that YaST routing entries were persistent. Anyone can help me?

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

If you like to use a GUI I think you better use the Network Manager GUI, I have some static routes there for an interface and that works.

Yast will be phased out so even if this is a real problem there is likely no enthusiasm to get this solved

1 Like

Thanks! Does that mean I need to move from Wicked to Network Manager? Is the GUI you mention a package I can find in Zypper?

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.

1 Like

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?

On Leap 15.6:
Here on wicked(Yast2):

cat /etc/sysconfig/network/ifroute-br0
default 192.168.0.254 - br0

All enabled via Yast2.

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 

If you are using already Cockpit you could check that yourself but it looks to me there is no support for that (yet).

@marianodaniel:

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:


> ip route show

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” …