From: Thomas Graf <tgraf@suug.ch>
To: acme@ghostprotocols.net
Cc: Stephen Hemminger <shemminger@osdl.org>,
Patrick McHardy <kaber@trash.net>,
"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, 4 May 2005 01:08:24 +0200 [thread overview]
Message-ID: <20050503230824.GS577@postel.suug.ch> (raw)
In-Reply-To: <39e6f6c70505031555691daf80@mail.gmail.com>
* Arnaldo Carvalho de Melo <39e6f6c70505031555691daf80@mail.gmail.com> 2005-05-03 19:55
> [root@toy acme]# route -n
> Tabela de Roteamento IP do Kernel
> Destino Roteador MáscaraGen. Opções Métrica Ref Uso Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 172.20.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 192.168.1.2 0.0.0.0 UG 0 0 0 eth0
> [root@toy acme]# uname -r
> 2.6.11-77124cl
> [root@toy acme]#
>
> [root@toy acme]# ip r s
> 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.192
> 172.20.0.0/16 dev tun0 proto kernel scope link src 172.20.0.1
> 127.0.0.0/8 dev lo scope link
> default via 192.168.1.2 dev eth0
Your distribution, scripts, whatever doesn't use the local table
for the loopback route. This gets to be a problem once you add
fib rules and rely on the fact that local routes should have top
priority.
> [root@toy acme]#
>
> [root@toy acme]# cat /proc/net/route
> Iface Destination Gateway Flags RefCnt Use Metric
> Mask MTU Window IRTT
> eth0 0001A8C0 00000000 0001 0 0 0
> 00FFFFFF 0 0 0
> tun0 000014AC 00000000 0001 0 0 0
> 0000FFFF 0 0 0
> lo 0000007F 00000000 0001 0 0 0
> 000000FF 0 0 0
> eth0 00000000 0201A8C0 0003 0 0 0
> 00000000 0 0 0
> [root@toy acme]#
Yes, that's the main routing table. This is a userspace issue.
next prev parent reply other threads:[~2005-05-03 23:08 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 [this message]
2005-05-03 22:58 ` Patrick McHardy
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=20050503230824.GS577@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=acme@ghostprotocols.net \
--cc=davem@davemloft.net \
--cc=kaber@trash.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.