At 03:44 PM 5/12/2008, Christer Solskogen wrote:
Derek Ragona wrote:
You may want to do traceroutes from the systems that do find the 0.0.0.0
interface. I would bet you have a default route and/or netmask sending
the traffic. You will get those arp messages if you run two different
interfaces on the same system, on the same subnet (not to be confused
with running multiple IP's on an interface.) Arp tries to tie an IP
address to a machine address, but if the reverse routing isn't correct
you will see these error messages.
A tip from George Davidovich setting the aliases to use netmask to
0xffffffff seems to fix the problem.
--
chs
Yes aliases should have a netmask of 255.255.255.255
-Derek
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
