Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!think!ames!ucbcad!ucbvax!amdcad!phil From: phil@amdcad.UUCP (Phil Ngai) Newsgroups: comp.dcom.lans Subject: Re: Milking machine performance/function Message-ID: <13930@amdcad.UUCP> Date: Tue, 2-Dec-86 04:05:31 EST Article-I.D.: amdcad.13930 Posted: Tue Dec 2 04:05:31 1986 Date-Received: Tue, 2-Dec-86 10:07:14 EST References: <1612@batcomputer.tn.cornell.edu> Reply-To: phil@amdcad.UUCP (Phil Ngai) Distribution: na Organization: Advanced Micro Devices, Sunnyvale, California Lines: 49 In article <1612@batcomputer.tn.cornell.edu> swb@batcomputer.UUCP (Scott Brim) writes: > >Does Bridge understand UDP RIP yet? (I suspect Cisco still only uses >its own proprietary routing protocol.) None of the Bridge boxes we have, which consist of GS/3 internet routers and CS/100 terminal servers, understand Berkeley's routed protocol. I think this is what you mean by UDP RIP. I don't know that my terminology is more accurate than yours but vendors seem to understand me better when I say Berkeley routed rather than RIP. Bridge Comm's lack of routed is a problem in several ways. Because they don't send routed packets, managing routing tables for our 100 hosts is very inconvenient. We have implemented a workaround for this by using a host which allows forging IP source addresses. We impersonate the GS/3 internet routers and advertise the networks available through them. This has been running for only a few days but seems like it will suffice for us. It was surprisingly easy. A shell script was used to assemble the packets and then send them to a raw Ethernet device. This system allows us to keep 100 hosts run by many different system managers up to date on routing information by changing just one file on one host. This system is not perfect. There would be benefit from the GS/3s producing the routed packets themselves. For example, if one gateway went down and an alternative route was available, hosts would automatically use the alternative. A worse problem is that the GS/3s don't listen to routed packets. We have started installing Apollo domain rings with Ethernet gateways. These gateways broadcast routed packets and if the GS/3 heard them, they would route packets destined for a node on a ring to the appropriate gateway. Instead, we have to get on a CS/100, use a nonstandard protocol and modify the GS/3. Every time we install a new Apollo ring, we have to update all eight of our GS/3s. Most times we have to add two entries for every new Apollo ring because of our redundant topology. Every time we install a new version of GS/3 software, we have to type in the entire routing table to each GS/3. It gets very tiresome. I wish I could store the routing tables as files on my VAX Unix machine and download them. I could probably figure out how by looking at the packets with my LANalyzer but haven't had time yet. -- If you had everything, where would you put it? Phil Ngai +1 408 749 5720 UUCP: {ucbvax,decwrl,hplabs,allegra}!amdcad!phil ARPA: amdcad!phil@decwrl.dec.com