Re: loopback routing - just curious

[Mirek Kwasniak <mirek@zind.ikem.pwr.wroc.pl>]

On Wed, Feb 23, 2000 at 03:42:19AM +0800, da Bobstopper wrote:
> hiya, i've noticed that 
> 
> route add -net 127.0.0.0
> 
> doesn't seem to work anymore and, even more curiously, doesn't seem to be
> needed. i can still ping 127.0.0.1 but the 127.0.0.0 route isn't evident in
> my route -n output.
> 
> i gather that this is kernel related, not debian related since it only happens
> after upgrading the default slink kernel to 2.2.10, but i'm still curious. 
> 
> removing the 127.0.0.0 route from the older 2.0.36 kernel machines prevents
> me from pinging 127.0.0.1. i like it, but what happened?

1) Routes based on IP and mask are added automatically in 2.2.x.
2) ifconfig, route (, ...) have now only basic compatybility with 2.2.x.
   Most powerfull are iproute (/sbin/ip) + ipchains utilities:

$ ip route list table all|grep 127
broadcast 127.255.255.255 dev lo  table local  proto kernel  scope link  src 127.0.0.1
broadcast 127.0.0.0 dev lo  table local  proto kernel  scope link  src 127.0.0.1
local 127.0.0.1 dev lo  table local  proto kernel  scope host  src 127.0.0.1
local 127.0.0.0/8 dev lo  table local  proto kernel  scope host  src 127.0.0.1

Mirek