[comp.bugs.4bsd] Problems starting vv0 Proteon PROnet-10 driver

herber@bgsuvax.UUCP (08/04/87)

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.