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):


	128.89.0.0    -----------    192.168.246.0      -------
	-------------|     A     |---------------------|   B   |
		      -----------                       -------

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

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

ifconfig le0 inet 128.89.1.133 ; ifconfig le0 inet alias 192.168.246.3

(there is no hostname.le0 file)

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

Despite what ifconfig says, there is clearly something in the client
that wants to use 192.168.246.3 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?