I have, in /lib/ndb/local
sys=p9cpu dom=tackle.hq.iba.co.za
ip=172.24.16.12 ether=0050043d4ed3
ip=196.30.44.147 ether=0050228dfee3
ipgw=196.40.44.129
proto=il
which has the following effect:
term% ndb/query ether 0050043d4ed3 ip
172.24.16.12
term% ndb/query ether 0050228dfee3 ip
196.30.44.147
I could not wish for better. However, having tried
ip/ipconfig -N /net/ether0
in /rc/bin/cpurc, where
cpu% cat /net/ether0/addr
0050043d4ed3
cpu% cat /net/ether1/addr
0050228dfee3
followed later by another
ip/ipconfig -N /net/ether1
both /net/ipifc/[01]/status return the 196.30.44.147
setting.
Naturally, there are complicating circumstances, like a DHCP server
that responds to
ip/ipconfig /net/ether0
and sets things up the way I want them, when I use this option
instead of the above.
But I wonder why the first version does not have the desired effect.
Should I do more experimenting, and should I be looking for a problem,
or am I merely misunderstanding something?
++L
