Re: bin/44032: pppd: proxyarp is not working

[Egervary Gergely <gergely%egervary.hu@localhost>]

The following reply was made to PR bin/44032; it has been noted by GNATS.

From: Egervary Gergely <gergely%egervary.hu@localhost>
To: Christos Zoulas <christos%zoulas.com@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, gnats-admin%netbsd.org@localhost, 
 netbsd-bugs%netbsd.org@localhost
Subject: Re: bin/44032: pppd: proxyarp is not working
Date: Tue, 04 Dec 2012 23:21:01 +0100

  > | - The proxy arp entries are not visible in `arp -a'. Should not they
  > | be visible? For example, on Linux they are visible.
  >
  > should be visible I think. do you have a configuration for me to test?
  >
  > | - Once I add an arp entry with `arp -s 10.0.0.192 <mac> pub proxy'
  > | I cannot remove it later. (arp: delete: can't locate 10.0.0.192)
  > | Is this normal?
  >
  > Works for me:
 
 It has something to do with the ppp interface. Try setting an arp entry
 on a ppp interface.
 
 Test #1: non existent IP address
 
 # arp -s 10.11.12.13 2c:27:d7:14:54:17 pub proxy
 # arp 10.11.12.13
 ? (10.11.12.13) at 2c:27:d7:14:54:17 on vlan10 permanent published 
 (proxy only)
 # arp -d 10.11.12.13
 
 All is good.
 
 Test #2: IP address of a ppp link (local endpoint)
 
 # arp -s 10.0.0.192 2c:27:d7:14:54:17 pub proxy
 # arp 10.0.0.192
 arp: 10.0.0.192 (10.0.0.192) -- no entry
 # arp -d 10.0.0.192
 arp: delete: can't locate 10.0.0.192
 
 It fails, but "something" is in the arp table. If I try to re-add the
 entry:
 
 # arp -s 10.0.0.192 2c:27:d7:14:54:17 pub proxy
 arp: set: proxy entry exists for non 802 device
 
 Maybe the entry is set up on the wrong interface?
 
 -- 
 Gergely EGERVARY