Bug 130186 (IT#45181) - initscripts doesn't add network route for loopback interface
Summary: initscripts doesn't add network route for loopback interface
Keywords:
Status: CLOSED NOTABUG
Alias: IT#45181
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: initscripts
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-17 19:40 UTC by Alexandre Oliva
Modified: 2014-03-17 02:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-08-17 20:58:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alexandre Oliva 2004-08-17 19:40:01 UTC
have a machine with at least one nic configured.
put the following rpm in the current directory:
initscripts-7.31.13.EL-1.i386.rpm  
initscripts-7.31.15.EL-1.i386.rpm

$rpm -q initscripts
initscripts-7.31.13.EL-1
$service network stop; service network start
$route | grep "^127.0"
127.0.0.0       *               255.0.0.0       U     0      0        0 lo
$service network stop
$rpm -Uvh initscripts-7.31.15.EL-1.i386.rpm
$service network start
$route | grep "^127.0"

By the way, "service network restart" behave the same way.

Comment 2 Bill Nottingham 2004-08-17 19:55:14 UTC
Does this actually affect functionality?

Comment 4 Alexandre Oliva 2004-08-17 20:39:19 UTC
I can't think of any use for sucn entries, but customer asked and I
couldn't see that the change was intentional.  Now that I got my patch
unreversed (doh!), I can see the removal of the `ip route replace'
command, and I understand why it was changed (such that multiple
interfaces on the same network don't get broken routing tables), so I
guess we can just leave it alone.


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