| To: | Zdenek Radouch <zdenek@xxxxxxx> |
|---|---|
| Subject: | Re: Do you know the TCP stack? (127.x.x.x routing) |
| From: | Thomas Graf <tgraf@xxxxxxx> |
| Date: | Sun, 6 Mar 2005 18:31:45 +0100 |
| Cc: | Martin Mares <mj@xxxxxx>, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx |
| In-reply-to: | <E1D7zBN-0004hX-00@xxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <E1D7lQN-0002gz-00@xxxxxxxxxxxxxxxxxxxxxxx> <E1D7lQN-0002gz-00@xxxxxxxxxxxxxxxxxxxxxxx> <E1D7zBN-0004hX-00@xxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
> Hmmm, I don't seem to have the loopback interface...
> This table implies that 127.0.0.1 should go out via eth0
> to a gateway 192.168.13.264. That's hard to believe.
It's in the local table
tgr:axs ~ ip route list dev lo table local
broadcast 127.255.255.255 proto kernel scope link src 127.0.0.1
broadcast 127.0.0.0 proto kernel scope link src 127.0.0.1
local 127.0.0.1 proto kernel scope host src 127.0.0.1
local 127.0.0.0/8 proto kernel scope host src 127.0.0.1
tgr:axs ~ ip route del 127.0.0.1 dev lo table local
tgr:axs ~ ip route del 127.0.0.0/8 dev lo table local
tgr:axs ~ ip route get 127.0.0.1
127.0.0.1 via 192.168.23.13 dev eth0 src 192.168.23.1
cache mtu 1500 advmss 1460 metric10 64
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Do you know the TCP stack? (127.x.x.x routing), alex |
|---|---|
| Next by Date: | Re: [PATCH 3/3 XFRM]: Fix invalid key for lookup of cached bundles, Patrick McHardy |
| Previous by Thread: | Re: Do you know the TCP stack? (127.x.x.x routing), alex |
| Next by Thread: | Re: Do you know the TCP stack? (127.x.x.x routing), Zdenek Radouch |
| Indexes: | [Date] [Thread] [Top] [All Lists] |