Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!RICE.EDU!almes From: almes@RICE.EDU (Guy Almes) Newsgroups: comp.protocols.tcp-ip Subject: Re: Many things on ethernet together??? Message-ID: <8805101325.AA15092@iapetus> Date: 10 May 88 13:25:13 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 10 RD: The key point here is that ethernet is a ``local area network'' technology, and that its designers *never* intended it to be a wide area network. This is not to say that long-distance bridging is never the right thing to do, but only that you should not be surprised when it exhibits limits. This idea of `local' suggests, not only physically proximity, but also adminstrative unity. In your case, it wasn't the physical distance, but the administrative distance that caused the problems. If you stay with the single pseudo-ethernet bridged approach, then you will need to have admini- strative structures that treat it as a single ethernet. -- Guy