Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!ames!ucbcad!ucbvax!excelan.UUCP!chuck
From: chuck@excelan.UUCP (Chuck Kollars, )
Newsgroups: comp.protocols.tcp-ip
Subject: posting for moderated news group protocols.tcp-ip
Message-ID: <8708190020.AA27806@mtxinu.UUCP>
Date: Tue, 18-Aug-87 17:15:21 EDT
Article-I.D.: mtxinu.8708190020.AA27806
Posted: Tue Aug 18 17:15:21 1987
Date-Received: Thu, 20-Aug-87 06:27:51 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 31

Subject: 2 IP's on 1 LAN
Keywords: TCP-IP Vitalink MAC-Bridge Ethernet

The need to have 2 logically separate IP networks on a single
datalink (specifically, an Ethernet LAN) for administrative reasons 
has arisen.  
 [Examples:
   a) Some nodes on a LAN have officially assigned IP addresses 
      because they sometimes interoperate with another network.  To
      conserve IP addresses, other nodes on the same LAN are assigned 
      IP addresses from a separate address space.  
   b) Two networks which are geographically separated, and which have
      been administered separately, are now being connected by a
      Vitalink datalink-level MAC-bridge.]  

Based on experience with similar situations, is the best course of 
action to:
  1) Modify the IP routing algorithm in each node to understand the
     notion of a "direct" route.  

  2) Reassign IP addresses so that all nodes have the same IP network
     number.  

  3) Install separate devices which act as fake gateways.  

  4) Other

--------------------------------------------------------------------
Chuck Kollars   - address for direct mail responses:  
  arpa:  mtxinu!excelan!chuck@ucbvax.berkeley.edu
  uucp:  ...ucbvax!mtxinu!excelan!chuck