routed(8) & arplookup brain-death on i386-current?

[Adam N. Thompson, MCNE]

I'm running i386-current as of Jan. 25 (AFAIK) and have encountered a
rather distressing problem:
routed(8) will not send out routes!

I'm running a custom kernel, unfortunately, so I'm doing another cvs
update and re-configure from GENERIC tonight, to see if I can replicate
the problem with -current as of (now) and GENERIC.

What I see as syslog output is:
Jan 27 09:40:06 hyperion routed[5091]: setsockopt(IP_ADD_MEMBERSHIP
RIP): Can't assign requested address

AFAIK, multicast routing support is turned on, and it doesn't make any
difference whether mrouted is running or not.

On a related note, arp support seems to have gone haywire as well.
I'm getting non-stop messages like:
Jan 27 09:33:30 hyperion /bsd: arplookup: unable to enter address
for 207.161.253.38
and
Jan 27 09:23:49 hyperion /bsd: arplookup: unable to enter address
for 207.161.253.46

...only for those two addresses, apparently!

207.161.253.38 is a Lexmark Optra printer, with only one IP address and
a correct subnet mask.
207.161.253.46 is an HP NetServer running Red Hat Linux 6.1 - one
ethernet adapter answers to multiple addresses, including:
207.161.253.46, 64.4.84.54, and 64.4.84.55.

Any ideas on what's going wrong? The ARP problems seem to have exactly
one side-effect: I cannot ping those two addresses from the OpenBSD box
... but I can telnet to them!

The routed problem is a bit more troublesome - I had to reconfigure
everything to use static routes first thing this morning.

Thanks for any input...
-Adam

--
Adam Thompson, MCNE, MCSE, CWT, A+
Vice-President / Chief Technology Officer, Commerce Design Inc.
<atho...@commerced.com>
tel: (204) 942-1648, fax: (204) 989-8080, cell: (204) 782-6198