[Bug 895219] New: /etc/sysconfig/network/routes not set
https://bugzilla.novell.com/show_bug.cgi?id=895219 https://bugzilla.novell.com/show_bug.cgi?id=895219#c0 Summary: /etc/sysconfig/network/routes not set Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: wicked-maintainers@suse.de ReportedBy: bwiedemann@suse.com QAContact: qa-bugs@suse.de Found By: Development Blocker: --- on openSUSE 20140829 (x86_64) I used yast2 lan to configure extra routes
cat /etc/sysconfig/network/routes 192.168.0.0 192.168.11.5 255.255.0.0 - 10.0.0.0 192.168.11.5 255.0.0.0 -
cat /etc/sysconfig/network/ifcfg-enp1s0 BOOTPROTO='dhcp4' ...
but those routes seem to be ignored by wicked even when explicitly calling rcnetwork restart -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=895219 https://bugzilla.novell.com/show_bug.cgi?id=895219#c1 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |mt@suse.com InfoProvider| |bwiedemann@suse.com --- Comment #1 from Marius Tomaschewski <mt@suse.com> 2014-09-08 14:17:52 UTC --- Is there a IPADDR= field in the ifcfg-enp1s0 with an address matching the 192.168.11.x network? A gateway has to be on a directly attached network and there is no device route visible above / incomplete configuration. What does a "wicked --debug all show-config &>config.out" say? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=895219 https://bugzilla.novell.com/show_bug.cgi?id=895219#c2 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|bwiedemann@suse.com | Resolution| |INVALID --- Comment #2 from Marius Tomaschewski <mt@suse.com> 2014-09-09 17:25:01 UTC --- A gateway has to be on a directly connected network, that is you need either: - IPADDR from same network as 192.168.11.5 or - REMOTE_IPADDR=192.168.11.5 in case of point-to-point links or - device route for 192.168.11.5 Fix your config to e.g. an provide IPADDR and a device route for the gateway: * ifcfg-enp1s0: IPADDR=192.168.11.1/32 * routes: 192.168.11.5 - - enp1s0 192.168.0.0 192.168.11.5 255.255.0.0 - 10.0.0.0 192.168.11.5 255.0.0.0 - -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=895219 https://bugzilla.novell.com/show_bug.cgi?id=895219#c3 --- Comment #3 from Marius Tomaschewski <mt@suse.com> 2014-09-09 17:32:05 UTC --- Or using IPADDR from the same network as the gateway: * ifcfg-enp1s0: IPADDR=192.168.11.1/24 * routes: 192.168.0.0 192.168.11.5 255.255.0.0 - 10.0.0.0 192.168.11.5 255.0.0.0 - -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=895219 https://bugzilla.novell.com/show_bug.cgi?id=895219#c4 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |mfilka@suse.com Version|201408* |201409* Resolution|INVALID | --- Comment #4 from Bernhard Wiedemann <bwiedemann@suse.com> 2014-09-20 15:02:30 CEST --- yast2 lan does not allow to give IP-addr values for ethernet devices that are configured to use DHCP. However, it allowed to give an "additional address" which ended up in the config as IPADDR_0='192.168.11.149/24' which caused the ethernet device to still get the same addr as before from DHCP and made the additional routes work. btw: there is a use-case which some (but not too many) people have. I want to access networks that are available behind a different gateway (192.168.11.5 in this case), but can not add the routes on the default GW. And also I do want to use DHCP to have the ease-of-use to not having to provide IP, DNS and defaultgw which might need changing in case the default router is replaced. note that this is working on 12.3 with exactly the same configs (without having to use the IPADDR= workaround) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=895219 https://bugzilla.novell.com/show_bug.cgi?id=895219#c5 --- Comment #5 from Bernhard Wiedemann <bwiedemann@suse.com> 2014-09-20 15:04:56 CEST --- Created an attachment (id=607086) --> (http://bugzilla.novell.com/attachment.cgi?id=607086) bad config.out without IPADDR_0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=895219 https://bugzilla.novell.com/show_bug.cgi?id=895219#c6 --- Comment #6 from Bernhard Wiedemann <bwiedemann@suse.com> 2014-09-20 15:05:26 CEST --- Created an attachment (id=607087) --> (http://bugzilla.novell.com/attachment.cgi?id=607087) good config.out with IPADDR_0 workaround -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com