There seems to be a bug somewhere in the code related to generating ARP
requests in NetBSD 1.0. I'm using the ed driver; but I'm not sure whether
the bug is in the driver code or somewhere in the general ARP code.

If I assign several addresses to an interface (i.e., alias addresses),
it seems that the ARP requests that go out will always have the
lowest IP address assigned to the interface in the ar$spa (source
protocol address) field. This is a bother to start with, because
if I'm running on a certain subnet, but happen to be faking an
address on another subnet for compatability reasons, any Cisco
routers nearby will toss out the ARP requests (rather than respond
to them) unless they also have an address from that network on that
interface. (I can't think of an easy fix for this, though, and I'm
not even sure it can really be considered a bug.)

Unfortunately, it seems that even if I delete this problamatic
address from the interface, the ARP routes will continue to use it
as ar$spa! The machine has to be rebooted to clear this condition.
This definitely is a bug.

cjs
-- 
Curt Sampson    curt@portal.ca		Retrogrouch n. a person who spurns
Internet Portal Services, Ltd.		clipless pedals, and is still dubious
Vancouver, BC   (604) 257-9400		about whether indexed shifting is a
Info at http://www.portal.ca/		really good idea.