On Tue, Jun 14, 2016 at 5:49 PM, Brian Kantor <Brian(a)ucsd.edu> wrote:
  [snip] Should I
expect to see those make it to my router? 
 No, because there is a filter at UCSD which requires you to be registered
 in the 
AMPR.ORG DNS.  You are not.  Once that is in place you should be
 able
 to traceroute and ping your 44.44.107.1 address from anywhere on the great
 unwashed Internet.  I would register you but I don't know your callsign.
 
 
Aha! The missing link. N1URO is correct that he did tell me that six months
ago;
sadly I overlooked that in his email. I'll email him directly to add DNS
entries.
FWIW, my callsign is AC2OI.
In the meantime, if you set up a tunnel to another 44-net address, you
  should
 be able to ping it even though you're not in the DNS as the filter only
 affects
 non-44 inbound Internet traffic.  I often test tunnels by seeing if I can
 ping to 
n1uro.ampr.org, 44.88.0.9, which is dependably there. 
Thanks. With this, I'm able to configure a second tunnel on a second gif
interface
and ping 44.88.0.9. My current configuration:
# ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 32768
        priority: 0
        groups: lo
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
        inet 127.0.0.1 netmask 0xff000000
cnmac0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 44:d9:e7:9f:a7:64
        priority: 0
        groups: egress
        media: Ethernet autoselect (1000baseT full-duplex)
        status: active
        inet 23.30.150.141 netmask 0xfffffff8 broadcast 23.30.150.143
cnmac1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 44:d9:e7:9f:a7:65
        priority: 0
        media: Ethernet autoselect (1000baseT full-duplex)
        status: active
        inet 192.168.129.4 netmask 0xffffff00 broadcast 192.168.129.255
cnmac2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 44:d9:e7:9f:a7:66
        priority: 0
        media: Ethernet autoselect (none)
        status: no carrier
        inet 44.44.107.1 netmask 0xffffff00 broadcast 44.44.107.255
enc0: flags=0<>
        priority: 0
        groups: enc
        status: active
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33144
        priority: 0
        groups: pflog
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
        priority: 0
        groups: gif
        tunnel: inet 23.30.150.141 -> 169.228.66.251
        inet 23.30.150.141 --> 169.228.66.251 netmask 0xff000000
gif1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
        priority: 0
        groups: gif
        tunnel: inet 23.30.150.141 -> 24.147.182.8
        inet 23.30.150.141 --> 24.147.182.8 netmask 0xff000000
# netstat -rn -f inet
Routing tables
Internet:
Destination        Gateway            Flags   Refs      Use   Mtu  Prio
Iface
default            23.30.150.142      UGS        4     5573     -     8
cnmac0
23.30.150.136/29   23.30.150.141      UC         1       16     -     4
cnmac0
23.30.150.141      44:d9:e7:9f:a7:64  UHLl       0     5788     -     1
cnmac0
23.30.150.142      4a:1d:70:de:c3:5a  UHLc       2       40     -     4
cnmac0
23.30.150.143      23.30.150.141      UHb        0        0     -     1
cnmac0
24.147.182.8       23.30.150.142      UGHSP      0       53     -     8
cnmac0
24.147.182.8       23.30.150.141      UHP        0        0     -     8 gif1
44.44.107/24       44.44.107.1        C          0      249     -     4
cnmac2
44.44.107.1        44:d9:e7:9f:a7:66  UHLl       0       48     -     1
cnmac2
44.44.107.255      44.44.107.1        Hb         0        0     -     1
cnmac2
44.88.0.0/27       24.147.182.8       UGS        0       31     -     8 gif1
44.135.49.0/27     24.147.182.8       UGS        0        6     -     8 gif1
77.171.66.225      23.30.150.142      UGHS       0        2     -     8
cnmac0
127/8              127.0.0.1          UGRS       0        0 32768     8 lo0
127.0.0.1          127.0.0.1          UHl        0       10 32768     1 lo0
169.228.66.251     23.30.150.141      UH         0        0     -     8 gif0
178.33.213.221     23.30.150.142      UGHS       0        2     -     8
cnmac0
192.168/16         192.168.129.1      UGS        2        9     -     8
cnmac1
192.168.129/24     192.168.129.4      UC         1        0     -     4
cnmac1
192.168.129.1      24:a4:3c:05:57:b5  UHLc       1        2     -     4
cnmac1
192.168.129.4      44:d9:e7:9f:a7:65  UHLl       0       24     -     1
cnmac1
192.168.129.255    192.168.129.4      UHb        0        0     -     1
cnmac1
224/4              127.0.0.1          URS        0     2449 32768     8 lo0
#
I still haven't figured out a way to add multiple tunnels on a single 'gif'
interface; I'm not sure such a thing is possible. But it seems that one can
dynamically create an arbitrary number of them, so maybe it doesn't
matter. A modified RIP daemon modified for AMPR can keep a reference-counted
list of gateways and create/destroy interfaces as needed for BSD-based
systems.
Still, if someone else has done this already and knows a better way, please
do let me know.
Thanks!  73 de AC2OI
        - Dan C.