Red Hat Bugzilla – Bug 132861
Missing lo entry in routing table in RHEL Update 3
Last modified: 2007-11-30 17:07:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.3)
Description of problem:
The lo entry is missing from the routing table after update 3. I
reported this bug against FC2 also, and was reassigned to stunnel but
I'm not convinced that is necessarily where the problem is.
Destination Gateway Genmask Flags Metric Ref
10.1.2.0 * 255.255.255.0 U 0 0
default router 0.0.0.0 UG 0 0
This bug does not exist after a CD installation. I'm 99% sure it
started after update 3.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RHEL then run up2date to get to "Update 3" status.
2. Issue "route" command.
Actual Results: Routing table is missing the entry for "lo".
Expected Results: I would expect a "lo" entry.
When I originally reported this against FC2 I used RHEL 3 as a
reference and the "lo" entry was there then. That was about a month
ago before the update 3 set of updates.
Now the "lo" entry is missing from RHEL 3 as well.
A commenter in the FC2 bug 129365 said that a fresh CD install of FC2
had the "lo" entry, but that it got killed running up2date and
updating. I can't confirm that though as I only noticed the problem
after many updates had been made.
I must admit that the system seems to work fine without the entry. I
am concerned by side effects as yet undescovered though.
In the FC2 thread Red Hat reassigned the bug to stunnel so I am
reporting against stunnel here (but stunnel has not been updated in
RHEL 3 !!).
Is this issue a bug?
FC2 and FC3 both have missing lo entries. Can we assume this is
normal and expected behavior from now on? Reclassify as "NOTABUG" ??
$ /sbin/ip addr ls
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
127/8 is treated as a local host IP address, a routing table entry is