Red Hat Bugzilla – Bug 85011
GUI creates route files that boot scripts can't see if interface nicknames used
Last modified: 2008-05-01 11:38:05 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830
Description of problem:
When using the redhat-config-network gui, the files creates route files with the
nickname (vs ethX). However, ifup-routes relies on the ethX name to find the
interface routes. As a result interface specific static routes will not be read
My system has eth1 nicknamed InternalInterface. Interface specific routes are
listed in /etc/sysconfig/networking/devices/InternalInterface.routes.
ifup-routes looks for eth1.routes and doesn't see InternalInterface.routes.
This is especially troublesome if you create an interface with static routes
then nickname the interface. Static routes will always be set to the initial
ones no matter how much you try to change them with the GUI due to the fact that
the new route table config isn't loaded
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a new ethernet interface
2. Give the interface a nickname
3. Set some static routes on the interface
5. Check routes with route command
Actual Results: Interface specific static routes will not appear in the route table
Expected Results: Interface spedific routes will appear in the route table
Copying the /etc/sysconfig/networking/devices/nickname.route file to
/etc/sysconfig/networking/devices/ethX.route will work as a workaround.
fixed in CVS
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.