Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!bonnie!akgua!sdcsvax!sdcrdcf!hplabs!sri-unix!sventek@LBL.ARPA From: sventek@LBL.ARPA Newsgroups: net.unix-wizards Subject: Re: second UBA blues Message-ID: <11804@sri-arpa.UUCP> Date: Fri, 2-Nov-84 00:45:37 EST Article-I.D.: sri-arpa.11804 Posted: Fri Nov 2 00:45:37 1984 Date-Received: Mon, 29-Oct-84 03:17:00 EST Lines: 15 A hearty thanks to Rick Adams for pointing out my problem. It seems that our 4.2 system was attempting to access a variable using NUBA+1. The fix is to declare that we have 4 uba's in the config file (as the generic system does), knowing that it will only find 2 nexi associated with an UBA. System came up like a champ, and has given us no problems. A minor gotcha for those considering embarking on the second UBA path and which have hosts with more than one network interface. If you plan on spreading your network interfaces over the two UBA's, you MUST place the interface whose address you want used for originated IP packets on UBA0. This is independent of the order in which the devices are listed in the configuration file. As it stands now, most of our r* protocol use is broken until I reboot with our Imp interface bound to UBA0. Joe Sventek