🚀 go-pugleaf

I've been trying long and hard to make arp proxy work with my 1200/9600 
baud gateway, wd6ehr-3.  I used "route add <9600-stn> 96", arp publish
<9600-stn> ax25 wd6ehr-3 (and all the hosts.net variants - it always 
comes up listed [44.16.0.21]), route add default 2m (my 1200 baud port); 
and the stations on 9600 use "route add default 96 wd6ehr-3", and separate 
"route add"'s for other stations on 9600.

Using this, when my gateway (pe1chl net) would send to the 9600 stations, 
the address field was always:
WD6EHR-3 > WD6EHR-3 :, etc; with the /ip addresses properly in the field 
_below_ the ax25 addresses.  Problem is - the other 9600 stations won't 
respond to this.

I've tried _many_ other tricks and suggestions, but the only thing that 
has worked thus far is setting up a dummy gateway for each station, 
using a second .ampr.org address, i.e. [44.16.0.175], and having the 
other station use "arp publish [44.16.0.175] ax25 wd6ehr-7" (in the case 
of my second 9600 station, wd6ehr-7, [44.16.0.22]).  _EACH_ station must 
use a _different_ "dummy" address for this to work!

I've exhausted the available docs ;-}, and local /ip guru's, and hope 
that someone who understands the arp process more than I (which doesn't
narrow the field terribly :-) can 1. tell me a simpler, less wasteful 
way to do this, and 2. perhaps explain the arp process in "big dummy-ese".

BTW, the route-add/arp-publish above works fine for slip - but not ax25
encapsulated /ip.

73, Mike wd6ehr@n6yn.#soca.ca.usa
internet: wd6ehr.ampr.org!wd6ehr@puffin.UUCP
7921 Wilkinson Avenue
North Hollywood CA 91605-2210
(818) 765-2857  (evenings except Tuesday)
Compu$erve 73240,3523