Re: 8.0-BETA4 not responding to ARP for published entries

Hi,

At Mon, 14 Sep 2009 21:50:47 -0700, Li, Qing wrote:
> Hi,
> 
> Please try patch at 
> 
>    http://people.freebsd.org/~qingli/proxy-arp-patch.diff
> 
> -- Qing

Thanks for taking care of it.

I tried it, and now proxy arp works on the patched FreeBSD
8.0-CURRENT-200902/amd64 as expected.  Thanks!

Could it be considered important enough to make it into
8.0-RELEASE at this final stage?  Hope it will, but if not,
please consider to point it out in the release note.

Hiroharu Tamaru


> -----Original Message-----
> From: owner-freebsd-net_at_freebsd.org on behalf of Hiroharu Tamaru
> Sent: Mon 9/14/2009 6:34 PM
> To: freebsd-net_at_freebsd.org
> Subject: Re: 8.0-BETA4 not responding to ARP for published entries
>  
> 
> 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_at_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