At 12:55 PM 5/12/2008, Christer Solskogen wrote:
Christer Solskogen wrote:
Derek Ragona wrote:

Sounds like you have 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 the advice.
OpenBSD box - where is resolving to.
        lladdr 00:01:c0:03:7c:09
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet6 fe80::201:c0ff:fe03:7c09%rl0 prefixlen 64 scopeid 0x1
        inet netmask 0xffffff00 broadcast
nfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 00:18:f3:29:d8:15
        inet netmask 0xffffff00 broadcast
        inet netmask 0xffffff00 broadcast
        inet netmask 0xffffff00 broadcast
        media: Ethernet autoselect (1000baseTX <full-duplex,flag0,flag1>)
        status: active

(I also have a Mac OX 10.5 which also resolves to But a windows machine do not resolve

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 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.

_______________________________________________ mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to