Date: Mon, 14 Sep 2009 21:50:47 -0700 From: "Li, Qing" <qing.li@bluecoat.com> To: "Hiroharu Tamaru" <tamaru@myn.rcast.u-tokyo.ac.jp>, <freebsd-net@freebsd.org>, <erikk@berkeley.edu>, <ccowart@rescomp.berkeley.edu> Cc: freebsd-current@freebsd.org Subject: RE: 8.0-BETA4 not responding to ARP for published entries Message-ID: <B583FBF374231F4A89607B4D08578A43046736AD@bcs-mail03.internal.cacheflow.com> References: <20090914174309.GF37291@hal.rescomp.berkeley.edu> <sa61vm97zyk.wl%tamaru@myn.rcast.u-tokyo.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Please try patch at=20 http://people.freebsd.org/~qingli/proxy-arp-patch.diff -- Qing -----Original Message----- From: owner-freebsd-net@freebsd.org on behalf of Hiroharu Tamaru Sent: Mon 9/14/2009 6:34 PM To: freebsd-net@freebsd.org Subject: Re: 8.0-BETA4 not responding to ARP for published entries =20 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. >=20 > $ arp -s 172.16.132.100 00:0c:29:16:bd:49 pub >=20 > 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, >=20 > I'm trying to setup an proxy arp on a dual homed host. >=20 > 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. >=20 > Here is a simple demonstration using two single-interfaced hosts: >=20 > 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 >=20 > 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 >=20 > 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 >=20 > 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: >=20 > 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 >=20 > arp who-has 192.168.0.12 tell 192.168.0.1 > ---->no reply >=20 > 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 >=20 > 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 >=20 > 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. >=20 > What am I missing? >=20 > Thanks. > --=20 > Hiroharu Tamaru _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B583FBF374231F4A89607B4D08578A43046736AD>