Bug 60361 - ifup add route when no route exists
ifup add route when no route exists
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-02-26 12:53 EST by Andres Grino
Modified: 2014-03-16 22:25 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-29 15:40:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andres Grino 2002-02-26 12:53:27 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Description of problem:
ifup allways add a route for a non-aliases interface, even when the interface 
doesn't connect to a "proper" segment. Example: eth2 connect to a DMZ segment 
with machines having IP addresses taken from the segment connected to eth1 
interface (and you use proxy-arp to let machines from eth1 and eth2 segments 
think they are on the same wire).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Define eth1 with ip, netmask
2. Define eth2 with ip, netmask (yes, because we 
really don't have a segment here)
3. service network restart

Actual Results:  Route to is thru eth2 now.
Whoo!!! we just changed the default route.

Expected Results:  No route added at all.
We except that a netmask of in ifcfg-ethN means "no network 
We solved it changing line 236 in ifup script from:
   if [ "${ISALIAS}" = no ] ; then
   if [ "${ISALIAS}" = no -a "${PREFIX}" != "32"] ; then
because, after all, there is no point in adding/replacing a route when the 
netmask is

Additional info:

While our net design may be a little non-ortodox, that scheme work in RedHat 
7.1 and earlier.
Comment 1 Bill Nottingham 2005-09-29 15:40:20 EDT
Closing bugs on older, no longer supported, releases. Apologies for any lack of

If this persists on a current release, such as Fedora Core 4, please open a new bug.

Note You need to log in before you can comment on or make changes to this bug.