[Bug 1202658] New: wicket ignores configured static routes when using dhcp
http://bugzilla.opensuse.org/show_bug.cgi?id=1202658 Bug ID: 1202658 Summary: wicket ignores configured static routes when using dhcp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs@suse.de Reporter: ralf.habacker@freenet.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Configured static routes are not applied to Linux hosts running the current openSUSE Tumbleweed x86_64 inside a virtualbox instance that contain a single network card and obtain their IP address via dhcp. Configuration: $ cat /etc/sysconfig/network/ifcfg-enps03 BOOTPROTO='dhcp4' STARTMODE='auto' $ cat /etc/sysconfig/network/ifroute-enps03 10.2.1.1/32 10.1.1.252 - enps03 $ grep '^[A-Z]' /etc/sysconfig/network/config AUTO6_WAIT_AT_BOOT="" AUTO6_UPDATE="" LINK_REQUIRED="auto" WICKED_DEBUG="" WICKED_LOG_LEVEL="" CHECK_DUPLICATE_IP="yes" SEND_GRATUITOUS_ARP="auto" DEBUG="no" WAIT_FOR_INTERFACES="" FIREWALL="no" NM_ONLINE_TIMEOUT="30" NETCONFIG_MODULES_ORDER="dns-resolver dns-bind dns-dnsmasq nis ntp-runtime" NETCONFIG_VERBOSE="no" NETCONFIG_FORCE_REPLACE="no" NETCONFIG_DNS_POLICY="auto" NETCONFIG_DNS_FORWARDER="resolver" NETCONFIG_DNS_FORWARDER_FALLBACK="yes" NETCONFIG_DNS_STATIC_SEARCHLIST="" NETCONFIG_DNS_STATIC_SERVERS="" NETCONFIG_DNS_RANKING="auto" NETCONFIG_DNS_RESOLVER_OPTIONS="" NETCONFIG_DNS_RESOLVER_SORTLIST="" NETCONFIG_NTP_POLICY="auto" NETCONFIG_NTP_STATIC_SERVERS="" NETCONFIG_NIS_POLICY="auto" NETCONFIG_NIS_SETDOMAINNAME="yes" NETCONFIG_NIS_STATIC_DOMAIN="" NETCONFIG_NIS_STATIC_SERVERS="" WIRELESS_REGULATORY_DOMAIN='' $ ip addr (no real addresses displayed for security reasons) eth0: ... inet 10.1.1.30/24 $ ip route default via 10.1.1.250 dev enps03 proto dhcp 10.1.1.0/24 dev enps03 proto kernel scope link src 10.1.1.30 One visible symptom is that the status of the network service means that enps03 is not active: $ systemctl status network ��� wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled) Active: active (exited) since Tue 2022-08-23 10:07:06 CEST; 22h ago Process: 921 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS) Main PID: 921 (code=exited, status=0/SUCCESS) CPU: 46ms Aug 23 10:06:57 lxserver39 systemd[1]: Starting wicked managed network interfaces... Aug 23 10:07:06 LXSERVER39 wicked[921]: lo up Aug 23 10:07:06 LXSERVER39 wicked[921]: enps03 device-not-running Aug 23 10:07:06 LXSERVER39 systemd[1]: Finished wicked managed network interfaces. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202658
Ralf Habacker
http://bugzilla.opensuse.org/show_bug.cgi?id=1202658
Hans-Peter Jansen
http://bugzilla.opensuse.org/show_bug.cgi?id=1202658
http://bugzilla.opensuse.org/show_bug.cgi?id=1202658#c5
Ralf Habacker
The host _may_ receive something from DHCP server (at a random point of time compared to apply time of the static settings) _or_ _not_ and it _may_ (accidentially) provide also an IP address from a network that matches the gateway from the static setup _or_ _not_.
So you are saying that internally it is not ensured that locally defined static routes are applied only after the full configuration is received from the dhcp server ?
Because the static settings (static "lease") in ifroute files and the dhcp lease are two different leases "config sets" and applied independently of each other -- without conditions or dependencies between them.
This answers my question above
Both capable to provide the complete configuration and both need to be complete by themself.
Can an option be added to ensure that static routes are applied after receiving configuration from dhcp ?
The clean way is to fix the dhcp server config to provide the routes as described in bug 907495 to provide all routes via dhcp (e.g. classless routes option).
Sorry, but this is not an option in our case, because every time the route is
adjusted, the network would have to be restarted and clients would lose
connections.
The usual procedure in this case is:
1. activate the route manually with ip route
2. add the new route to /etc/sysconfig/network/routes or
/etc/sysconfig/network/ifroute-
participants (1)
-
bugzilla_noreply＠suse.com