Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!cbosgd!osu-eddie!bgsuvax!herber From: herber@bgsuvax.UUCP Newsgroups: comp.protocols.tcp-ip,comp.unix.wizards,comp.bugs.4bsd Subject: Problems starting vv0 Proteon PROnet-10 driver Message-ID: <1249@bgsuvax.UUCP> Date: Tue, 4-Aug-87 13:25:46 EDT Article-I.D.: bgsuvax.1249 Posted: Tue Aug 4 13:25:46 1987 Date-Received: Fri, 7-Aug-87 05:46:19 EDT Organization: Bowling Green State University B.G., Oh. Lines: 53 Keywords: proteon ifconfig phases_of_the_moon Xref: utgpu comp.protocols.tcp-ip:777 comp.unix.wizards:3302 comp.bugs.4bsd:448 OK, this is a good one...... I have 2 4.3BSD VAXen on an ethernet using Interlan interfaces (il0) and a Proteon, PROnet-10 using Proteon pronet interfaces (vv0). I have just changed from using class A address numbers (we didn't talk to anyone else in the world) to a class B Internet address using subnetting. Everything worked all along with the class A addresses. When I tried the following sequence of commands in /etc/rc.local, ifconfig vv0 inet 129.1.1.1 netmask 0xffffff00 ifconfig il0 inet 129.1.2.3 netmask 0xffffff00 ifconfig lo0 localhost the ifconfig for the vv0 interface fails with an "ifconfig: ioctl (SIOCSIFADDR): Can't assign requested address" and the internet address is left at 0.0.0.0. The netmast is correctly set at 0xffffff00 though (see below); # ifconfig vv0 vv0: flags=63,UP,BROADCAST,NOTRAILERS,RUNNING> inet: 0.0.0.0 netmask ffffff00 # If I try the EXACT SAME ifconfig vv0 statement AFTER the initial failure, it works and the address is correctly set at 129.1.1.1. I then switched the order of the statements in the /etc/rc.local to ifconfig lo0 localhost ifconfig il0 inet 129.1.2.3 netmask 0xffffff00 ifconfig vv0 inet 129.1.1.1 netmask 0xffffff00 and reboot, it works just fine the FIRST TIME........ ARGH!!!!!!!!! I looked at the if_vv.c driver and the error is returned to the ioctl() that is used in ifconfig to initialize the address. The error is returned in if_vv.c when the host node number on the board is not the same as that of the host number in the address. It looks to be some kind of a problem when using the subnetting/netmask features. Now that I found a combination that works, I will continue to use it but I would love to hear someone's opinion (guess, even:-) of why this doesn't work consistantly. -- Steve Herber CSNET herber@bgsu.edu Sr. Systems Programmer UUCP ...!osu-eddie!bgsuvax!herber Bowling Green State Univ.