Re: automatic routing in 2.2.*

From: Peter T. Breuer (ptb@it.uc3m.es)
Date: Tue Mar 28 2000 - 06:44:06 EST


"A month of sundays ago Paul Jakma wrote:"
> On Mon, 27 Mar 2000, Robert Manning wrote:
>
> > By definition: a network is defined by a single ip address and netmask
> > combination.
>
> very true, hadn't thought of it like that before, and can't argue around
> it.

Whatever, I'll put a network up when I want one, and I'll put an IP
address up when I want one. I most definitely DON'T want the machine to
put a network up for me when I don't say so. The current behaviour is
broken in several respects:

1) ifconfig lo:7 down downs lo
2) ifconfig lo up ups lo:7
3) routes and arp are changed when I put an alias up on lo:7 when I don't
   want this to be anything else but a dummy, visible only locally

The folowing situation shows a machine that responded ITSELF to pings
and telnet to its LOCAL alias, both from the machine itself and from
OUTSIDE (except from the real second host, of course ..).

eth0 Link encap:Ethernet HWaddr 00:60:97:BC:B3:CB
          inet addr:163.117.144.132 Bcast:163.117.144.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:302722 errors:0 dropped:0 overruns:0 frame:0
          TX packets:119133 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:10 Base address:0x6100

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:3924 Metric:1
          RX packets:6697359 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6697359 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

lo:7 Link encap:Local Loopback
          inet addr:163.117.144.200 Mask:255.255.255.255
          UP LOOPBACK RUNNING MTU:3924 Metric:1

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
163.117.144.0 0.0.0.0 255.255.255.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 163.117.144.2 0.0.0.0 UG 1 0 0 eth0

This is a bug. Kernel 2.2.10 in this instance, but I've seen it
elsewhere. Unfortunately I didn't get the arp tables before I lost
contact. But the whole net was being taken to this machine instead
of the 200 addresses real owner.

Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Mar 31 2000 - 21:00:21 EST