From owner-freebsd-net@FreeBSD.ORG Tue Sep 15 02:09:16 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A22C2106568B for ; Tue, 15 Sep 2009 02:09:16 +0000 (UTC) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from mailv3.ecc.u-tokyo.ac.jp (mailv3.ecc.u-tokyo.ac.jp [133.11.225.58]) by mx1.freebsd.org (Postfix) with ESMTP id 28FFC8FC2B for ; Tue, 15 Sep 2009 02:09:16 +0000 (UTC) Received: from mailv1.ecc.u-tokyo.ac.jp (mailv1.ecc.u-tokyo.ac.jp [133.11.225.59]) by mailv3.ecc.u-tokyo.ac.jp (Postfix) with ESMTP id 875AB6C028F for ; Tue, 15 Sep 2009 10:35:00 +0900 (JST) Received: from mhs002.ecc.u-tokyo.ac.jp (mhs002.ecc.u-tokyo.ac.jp [133.11.70.162]) by mailv1.ecc.u-tokyo.ac.jp (Postfix) with ESMTP id B87816C0043 for ; Tue, 15 Sep 2009 10:34:58 +0900 (JST) Received: from amulet.amuletic.net (124.155.55.252 [124.155.55.252]) by mhs002.ecc.u-tokyo.ac.jp (SpamBlock.pstn.b 3.4.102) with ESMTP id for ; Tue, 15 Sep 2009 10:34:47 +0900 Date: Tue, 15 Sep 2009 10:34:43 +0900 Message-ID: From: Hiroharu Tamaru To: freebsd-net@FreeBSD.org In-Reply-To: <20090914174309.GF37291@hal.rescomp.berkeley.edu> References: <20090914174309.GF37291@hal.rescomp.berkeley.edu> User-Agent: User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-IP: 124.155.55.252 X-FROM-DOMAIN: myn.rcast.u-tokyo.ac.jp X-FROM-EMAIL: tamaru@myn.rcast.u-tokyo.ac.jp Cc: Subject: Re: 8.0-BETA4 not responding to ARP for published entries X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2009 02:09:16 -0000 At Mon, 14 Sep 2009 10:43:09 -0700, Chris Cowart wrote: > We have a system which makes heavy use of published arp entries. I know > the arp code has been significantly overhauled in 8, but it looks like > this functionality is now broken. > > $ arp -s 172.16.132.100 00:0c:29:16:bd:49 pub > > If I watch tcpdump on the interface, I see arp requests come in but no > replies are sent. This is a clean build with no firewalls enabled. Just for another datapoint, I see the same symptom. I am currently running ports/net-mgmt/choparp as a workaround. At Thu, 23 Apr 2009 21:13:51 +0900, Hiroharu Tamaru wrote: > Subject: proxy arp on 8.0-current? > Date: Thu, 23 Apr 2009 21:13:51 +0900 > To: freebsd-net@freebsd.org > > Hi, > > I'm trying to setup an proxy arp on a dual homed host. > > I noticed that I cannot set it up on 8.0-current the same way as I > could on 6.2; hence the question: have the setup procedure changed > recently (when the arp table was separated from the routing table, > maybe?)? My 8.0-current is from 200902 snapshot. > > Here is a simple demonstration using two single-interfaced hosts: > > setup: > host6.2# ifconfig em0 inet 192.168.0.1/24 > host6.2# arp -s 192.168.0.11 auto pub > host6.2# arp -an | grep permanent > ? (192.168.0.1) at 00:16:d3:xx:xx:xx on em0 permanent [ethernet] > ? (192.168.0.11) at 00:16:d3:xx:xx:xx on em0 permanent published [ethernet] > host6.2# tcpdump -np arp > > host8.0# ifconfig em0 inet 192.168.0.2/24 > host8.0# arp -s 192.168.0.12 auto pub > host8.0# arp -an | grep permanent > ? (192.168.0.2) at 00:0c:29:xx:xx:xx on em0 permanent [ethernet] > ? (192.168.0.12) at 00:0c:29:xx:xx:xx on em0 permanent published [ethernet] > host8.0# tcpdump -np arp > > then, I do: > host6.2# arp -d 192.168.0.2; ping -c 1 192.168.0.2 > host6.2# arp -d 192.168.0.12; ping -c 1 192.168.0.12 > host8.0# arp -d 192.168.0.1; ping -c 1 192.168.0.1 > host8.0# arp -d 192.168.0.11; ping -c 1 192.168.0.11 > > I am not caring about 'arp -d' errors (cannot locate) nor ping not > responding (for proxied addresses). I just cared about arp requests and > replys for now. The output of tcpdump on both sides are like this: > > arp who-has 192.168.0.2 tell 192.168.0.1 > arp reply 192.168.0.2 is-at 00:0c:29:xx:xx:xx > > arp who-has 192.168.0.12 tell 192.168.0.1 > ---->no reply > > arp who-has 192.168.0.1 tell 192.168.0.2 > arp reply 192.168.0.1 is-at 00:16:d3:xx:xx:xx > > arp who-has 192.168.0.11 tell 192.168.0.2 > arp reply 192.168.0.11 is-at 00:16:d3:xx:xx:xx > > As you can see from the above, > 'arp -s 192.168.0.12 auto pub' on 8.0-current host > seems not to be producing proxy arp's. > > What am I missing? > > Thanks. > -- > Hiroharu Tamaru