From: Patrick McHardy <kaber@trash.net>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@oss.sgi.com
Subject: Re: [Bug 4554] New: /proc/net/route missing info for 127.0.0.1/8
Date: Wed, 04 May 2005 00:58:24 +0200 [thread overview]
Message-ID: <42780210.2070607@trash.net> (raw)
In-Reply-To: <20050503154709.218626c6@dxpl.pdx.osdl.net>
Stephen Hemminger wrote:
> It shows up on our 2.4.18 system, probably it got lost in the fib/seq_printf
> conversion.
>
> $ /sbin/route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.159.0 172.20.4.11 255.255.255.0 UG 0 0 0 eth2
> 172.20.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 172.20.0.1 0.0.0.0 UG 0 0 0 eth2
2.4.18 looks similar to 2.4.30 in fib_get_procinfo(), fib_magic() and
other functions involved. I believe its simply a change of how userspace
sets up the routes:
# route -n
172.16.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 172.16.0.1 0.0.0.0 UG 0 0 0 eth0
# route add -net 127.0.0.0/8 lo
# route -n
172.16.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 172.16.0.1 0.0.0.0 UG 0 0 0 eth0
"route" seems to add all routes to the main table. My debian system
relies on the kernel setting up loopback correctly, so it doesn't add
a route itself.
Regards
Patrick
prev parent reply other threads:[~2005-05-03 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 21:36 Fw: [Bug 4554] New: /proc/net/route missing info for 127.0.0.1/8 Stephen Hemminger
2005-05-03 22:41 ` Patrick McHardy
2005-05-03 22:47 ` Stephen Hemminger
2005-05-03 22:55 ` Arnaldo Carvalho de Melo
2005-05-03 23:08 ` Thomas Graf
2005-05-03 22:58 ` Patrick McHardy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42780210.2070607@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.