From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; sr-YU; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3 Description of problem: system-network-config lacks the ability to specify a default route with a metric. A scenario in which this is needed: I have a single network interface which sometimes can be used to obtain the network settings by DHCP. When it is not possible, the interface should get a fixed IP number. My resolution is as follows: - Use eth0 as the interface for DHCP; set its default route metric to be say 0 - Use eth0:1 as the interface for the fixed IP; set its default route metric to be 1 (note that the other way around is not possible, as eth0:1 does not support DHCP) Thus, when DHCP succeeds, its default route will override the fixed IP. When DHCP fails no default route for the DHCP gw will be set and the fixed IP will take over. This is at present not possible with s-c-n. Default routes override each other as the metric is always 0 so the default route would end up to be the one from the fixed IP setup, regardless of whether DHCP succeeded or not. Version-Release number of selected component (if applicable): system-config-network-tui-1.3.22-1 How reproducible: Always Steps to Reproduce: 1. Open s-c-n and verify that it is not possible to add the data about the default gw metric, and whether the link should set the gw or not (current default is that it always does) Additional info:
Even without this specific scenario, an user should be able to specify whether the default route should be established and with what metric. Yes, it may be an advanced setting, but it is necessary nevertheless.
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
https://hosted.fedoraproject.org/projects/system-config-network/ticket/43