From owner-freebsd-questions Mon Dec 13 16:46:24 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id DA66314C48 for ; Mon, 13 Dec 1999 16:46:16 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.9.3) id TAA75105; Mon, 13 Dec 1999 19:49:17 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199912140049.TAA75105@cc942873-a.ewndsr1.nj.home.com> Subject: Re: arplookup messages In-Reply-To: from Thierry Delaitre at "Dec 13, 1999 10:22:39 am" To: delaitt@cpc.wmin.ac.uk (Thierry Delaitre) Date: Mon, 13 Dec 1999 19:49:16 -0500 (EST) Cc: freebsd-questions@FreeBSD.ORG Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thierry Delaitre wrote, > > Hi, > > I use a FreeBSD box running FreeBSD 3.4-RC as a router and I keep getting > some arplookup messages. The routing of IP packets works properly but why > do I keep getting these messages ? I was using a FreeBSD 2.2.x box before > and I was not getting these messages at all. Any help would be > appreciated. Don't have a real solution, but I think I see the problem and I have one question (that might be a solution). > The network configuration of the 2 ethernet interfaces is described below > as well as the routing table. Please note that the netmasks for xl0 & xl1 > are both correct. Please also note that I use routed -s to manage the > routing table. > > xl0: flags=8843 mtu 1500 > inet 161.74.69.77 netmask 0xffffff00 broadcast 161.74.69.255 > ether 00:10:4b:46:80:9c > media: 100baseTX > supported media: autoselect 100baseTX 100baseTX > ex> 100baseTX 10baseT/UTP 10baseT/UTP > 10baseT/UTP > > xl1: flags=8a43 mtu 1500 > inet 161.74.70.30 netmask 0xfffffff0 broadcast 161.74.70.31 > ether 00:10:4b:46:81:1a > media: 10baseT/UTP > supported media: autoselect 100baseTX 100baseTX > ex> 100baseTX 10baseT/UTP 10baseT/UTP > 10baseT/UTP > > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif > Expire > default 161.74.69.1 UGSc 68 62993 xl0 > 127.0.0.1 127.0.0.1 UH 1 260 lo0 > 161.74.69/24 161.74.69.63 UGc 9 28713 xl0 ^^^^^^^^^^^^ Problem: According to this entry, your machine uses this host as a gateway to talk to 161.74.69/24. Thus, it cannot ARP for the machines below since it believes it has no layer 2 link to them, only an IP connection. (The entry 161.74.69/24 _should_ be 'link#1' analogous to the 161.74.70.16/28 entry below.) Question: Why are you running routed(8)? If you have a default gateway that never changes, the static 'default' entry above, I don't see what routed will do for you. I think turning off routed would fix your problem, but there may be some non-obvious reason you are using it. > 161.74.69.1 0:80:3e:5d:7f:e6 UHLW 64 0 xl0 1043 > 161.74.69.63 0:0:c0:b7:df:a1 UHLW 5 2677 xl0 291 > 161.74.69.77 0:10:4b:46:80:9c UHLW 15 64486 lo0 > 161.74.70.16/28 link#2 UC 0 0 xl1 > 161.74.70.29 8:0:20:72:48:fc UHLW 2 19082 xl1 234 > 161.74.70.30 0:10:4b:46:81:1a UHLW 0 1 lo0 > 161.74.70.31 ff:ff:ff:ff:ff:ff UHLWb 0 1 xl1 > > Dec 13 10:05:13 seth /kernel: arplookup 161.74.69.75 failed: host is not > on local network > Dec 13 10:14:01 seth /kernel: arplookup 161.74.69.78 failed: host is not > on local network > Dec 13 10:15:34 seth /kernel: arplookup 161.74.69.74 failed: host is not > on local network > Dec 13 10:17:59 seth /kernel: arplookup 161.74.69.70 failed: host is not > on local network -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message