12.3 YaST and routing malfunction

Using yast from a terminal.
YaST > Network Devices > Network Settings> Routing

Routing table entries can be modified with Add | Edit | Delete

These are then saved in /etc/sysconfig/network/routes
However these are not loaded/used following "systemctl restart network.service"
I can add routes with route add or ip route add, but do not know how to make them persistent in a systemd world. This all works fine on our production machines (11.4-evergreen). Is this just my screwed up 12.3 test machine, or is it for real?

I am with you that the parameters in */etc/sysconfig/network/routes *should be used in startinng the network.

Is this only when yi-ou start it manualy, or also on boot?
(this to fine tune an eventual bug report).

I was not sure about testing this remotely. But I am on a ferry on my way home with nothing better to do, so … Two at scripts. One to stop the network, rm /etc/sysconfig/network/routes* and /etc/sysconfig/network/ifcfg-eth*, then reboot. A second at to, hopefully, add a network interface and default gateway after the reboot. That was successful, so I was then able to use YaST to configure both interfaces, a default gateway and two additional routes. These persisted after both both systemctl restart network.service and a systemctl reboot.

So the conclusion is it was my screwed up test machine and not a real problem/bug.

Congratulations. A good thing you weren’t sea-sick on that ferry rotfl!

On 2013-03-26 11:46, eng-int wrote:
> Is this just my screwed up 12.3
> test machine, or is it for real?

This happened to me just after I installed 12.3 RC2, YaST was incapable
of setting up routes of any kind. It also wanted to install “smpppd”,
but this failed because there was no routing. After many tests, it
worked after running “rcnetwork restart”.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)