Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!sdcsvax!ucbvax!AI.AI.MIT.EDU!JBVB
From: JBVB@AI.AI.MIT.EDU ("James B. VanBokkelen")
Newsgroups: comp.protocols.tcp-ip
Subject: Re: More than one IP (sub)network on one ethernet cable
Message-ID: <303033.871222.JBVB@AI.AI.MIT.EDU>
Date: 23 Dec 87 00:49:47 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 12

One point I hadn't made in the earlier messages is that I am looking
at the issue from the standpoint of a single-user PC workstation.
We don't presently support more than one interface, and so we aren't
blessed with all the configuration issues (and problems) that a
multi-homed host has from the beginning.

Support for multiple networks on one cable (however primitive) seems
to be associated with multi-homedness, and I think I see why.  If I
wind up doing it, my routing code gets elaborate, but the primitive
O/S prevents me from taking much advantage of it.  Hi ho.

jbvb