At 12:55 PM 5/12/2008, Christer Solskogen wrote:
Christer Solskogen wrote:
Derek Ragona wrote:
Sounds like you have 0.0.0.0 configured on an ethernet interface. I
would check all your systems, and be sure it isn't used.
I checked, and there is no interface with that ip address. But thanks for
OpenBSD box - where 0.0.0.0 is resolving to.
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
media: Ethernet autoselect (100baseTX full-duplex)
inet6 fe80::201:c0ff:fe03:7c09%rl0 prefixlen 64 scopeid 0x1
inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
nfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
inet 192.168.0.3 netmask 0xffffff00 broadcast 192.168.0.255
inet 192.168.0.4 netmask 0xffffff00 broadcast 192.168.0.255
inet 192.168.0.5 netmask 0xffffff00 broadcast 192.168.0.255
media: Ethernet autoselect (1000baseTX <full-duplex,flag0,flag1>)
(I also have a Mac OX 10.5 which also resolves 0.0.0.0 to 192.168.0.1.
But a windows machine do not resolve 0.0.0.0)
Gah, my bad.
the nfe0 interface are not on OpenBSD, but on my FreeBSD box (where this
arp-messages shows up)
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.
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"