Subject: ifconfig hackery
To: None <port-sun3@NetBSD.ORG>
From: Tom Calderwood <tcalderw@BBN.COM>
List: port-sun3
Date: 10/31/1995 13:34:18
I am trying a hack with ifconfig on a diskless 3/50.  In particular,
during network startup I am trying to set the address of the ethernet
interface to be different from the address upon which it was nfs
booted.  Pictured below are A (the server) and B (the diskless
client):    -----------      -------
	-------------|     A     |---------------------|   B   |
		      -----------                       -------

B used to be on the network, but my experiments were
causing undesired activity on that net.  B is now isolated from, being on the second interface of A.  B must now boot
from the interface of A.  However, I would like B 
to still be able to use its assigned address to
communicate with systems on the other side of A.  I can make A
proxy ARP for B's address and I can route through A
to B's address and back.

My problem comes when B initiates network traffic for
In B's netstart file, I have the following line:

ifconfig le0 inet ; ifconfig le0 inet alias

(there is no hostname.le0 file)

If I do an ifconfig -a after the B comes up, it claims that le0 has
the address.  But tcpdump shows that the packets it sends
to destinations have the address as the IP 

Despite what ifconfig says, there is clearly something in the client
that wants to use as the primary address.  Does anyone
know where in the client code this is being caused and/or how it
could altered to do what I want?