ernie@nucsrl.UUCP (Ernest Woodward) (08/26/87)
In the past I requested information about the use of two DEQNA's on ULTRIX v1.2 and 4.3BSD and had received several replies with good information. Unfortunately, a system crash lost those mail notes and I was not able to send information back to specific individuals. Now I have a similar problem with the Mt Xinu's 4.3BSD and I thought I would post a note with another question and also supply some information of the past experiences. As mentioned by several respondents of my ULTRIX question, when booting off a kernel with a name other than /vmunix (e.g. /vmunix.new), the 'ps', 'netstat', etc. output does not get generated at the standard output file. I was able to run ULTRIX v1.2 with two DEQNA's and everything worked normally, as long as I booted off the kernel named /vmunix. My initial problem with use of two DEQNA's on the 4.3BSD system was caused by the following statement: /etc/ifconfig qe0 inet xx.xx.xx.xx broadcast xx.xx.xx.xx up -trailers The 'up' argument on this initial ifconfig command will cause the kernel to panic. As mentioned by the respondents of my 4.3BSD-2 DEQNA's question, the up argument should not be used on the initial ifconfig. I have now installed the Mt Xinu's 4.3BSD and have the following set of statements in my /etc/rc.local file concerning ETHERNET: /etc/ifconfig lo0 localhost /etc/ifconfig qe0 inet 192.26.85.1 broadcast 192.26.85.0 -trailers /etc/ifconfig qe1 inet 128.174.5.131 broadcast 128.174.5.0 -trailers I am able to boot the kernel up into single-user mode and perform several basic functions. I have been able to run ping over the qe1 ethernet and run all network utilities over the qe0 ethernet. The qe1 ethernet does not have enough currently active hosts to perform other networking tests. When I bring up multi-user mode, all the daemons get activated and the login prompts are available. Once a person log's on, they are shown /etc/motd and they get hung before the shell can give them a prompt. If I bring the system up with only the qe0 ethernet (i.e. remove the ifconfig qe1 statement from /etc/rc.local file), everything runs fine. As soon as I enter the /etc/ifconfig qe1 inet ... line, several (and maybe all) processes hang. I am using the MicroVAX II as a gateway machine to ARPANET and two ethernets. I am therefore running with two DEQNA's and ACC's ACP5250 (X.25 board for the qbus). I am running with the named and egp. I am not currently using routed, instead, we use /etc/route add defaults in several hosts on the network. I am concerned that there is some file somewhere in the system that limits the use of sockets or something unknown to me. If anyone has an idea, please send the information to: ernie@eecs.nwu.edu or ernie@accuvax.nwu.edu or ernie@nuacc.bitnet Thanks to all the people who have sent me some extremely valuable information in the past. Sincerely, Ernie Woodward Acting Manager of Computer Communications and Networking Academic Computing and Network Services Northwestern University