Kevin Stevens <[EMAIL PROTECTED]> writes: > On Saturday, Jan 11, 2003, at 08:28 US/Pacific, Lowell Gilbert wrote: > >> I think this is it: > >> > >> net.link.ether.inet.log_arp_wrong_iface > >> > >> Check whether yours is off or on and change it the other way. > > > > It would be better to fix the actual problem than to just make the > > error message go away. In this case, specifying a correct subnet mask > > on the alias configuration should solve the problem. [I think.] > > I saw the note about the incorrect mask on the second 10. address; and > agree that it needs fixing, but I don't think that was the source of > the log messages. I ran into the same thing when I had different NICS > on different IP subnets on the same physical network some time ago - > that's how I remembered the setting. That's why there's a sysctl for > it - depending on your configuration, it isn't actually an error.
The incorrect netmask would be enough to cause the message. And I happen to think that the message *always* indicates an error. In many cases, it indicates an ISP error that you (downstream) can't do anything about, but it's always an error. [My logic is: within the window of a single ARP timeout, an IP address should not be used on the link by a different Ethernet address. > Let's see what the OP discovers. I'm sure that one way or another, he's fine. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
