Date: Thu, 10 Dec 1998 15:14:44 +1030 From: Greg Lehey <grog@lemis.com> To: Briang <brian@briang.org>, FreeBSD <freebsd-questions@FreeBSD.ORG> Subject: Re: What does this mean ? Message-ID: <19981210151444.Z12688@freebie.lemis.com> In-Reply-To: <007801be23f7$6fbe7680$2900a8c0@brian-desktop.briang.org>; from Briang on Wed, Dec 09, 1998 at 08:41:17PM -0800 References: <007801be23f7$6fbe7680$2900a8c0@brian-desktop.briang.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, 9 December 1998 at 20:41:17 -0800, Briang wrote: > Dec 9 21:02:07 dns2 /kernel: arp: 192.168.0.41 is on tl1 but got reply from 00:80:5f:6f:7f:eb on tl0 > Dec 9 21:09:43 dns2 /kernel: arp: 192.168.0.41 is on tl1 but got reply from 00:80:5f:6f:7f:eb on tl0 > Dec 9 21:09:55 dns2 /kernel: arp: 192.168.0.41 is on tl1 but got reply from 00:80:5f:6f:7f:eb on tl0 Although it's correct to wrap normal text at about 70 characters, please don't do this for log messages. It's easier to read them in full length. > Why does this say xxx.41 is on TL1, and got reply from TL0 -> has > 10.26.200.1 on it > I get these errors every ten mins. This depends a bit on your network topology. > dns2# arp -a > ? (192.168.0.1) at 0:8:c7:72:1d:e3 > ? (192.168.0.41) at 0:80:5f:6f:7f:eb > > dns2# ifconfig -a > tl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet 10.26.200.1 netmask 0xffffff00 broadcast 10.26.200.255 > ether 00:80:5f:e6:92:2c > media: autoselect (10baseT/UTP <half-duplex>) > supported media: 100baseTX <full-duplex> 100baseTX <half-duplex> > 100baseTX 10baseT/UTP <full-duplex> autoselect 10base5/AUI This shows that tl0 handles a sub-class-A network 10.26.200.x. > tl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet 192.168.0.94 netmask 0xffffff00 broadcast 192.168.0.255 > ether 00:80:5f:e6:92:ac > media: autoselect (10baseT/UTP <half-duplex>) > supported media: 100baseTX <full-duplex> 100baseTX <half-duplex> > 100baseTX 10baseT/UTP <full-duplex> autoselect 10base5/AUI And, much more importantly, tl1 handles class C net 192.168.200.x. Any data from this network should come in on this network. > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 > inet 127.0.0.1 netmask 0xff000000 So basically, the question is to you: how come you're getting a physical (arp) connection from this machine on the wrong interface? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981210151444.Z12688>