[HamWAN PSDR] Connecting to 44.0.0.1 (or not)

[Tom Hayward]

44.0.0.1 is a weird case. That is the AMPR gateway, used by AMPR nodes
that don't have direct internet routing as HamWAN does. There's really
no case where you should need to contact that router. For Internet
stuff, you have a direct path; for 44net, HamWAN has tunnels to each
AMPR node.

A dumb static route at UCSD (the hop before 44.0.0.1) is set to
forward 44.0.0.0/8 back to 44.0.0.1. This router is dumb and doesn't
realize there's a more specific path to HamWAN. This means packets
from 44.0.0.1 have no way to get back to 44.24.240/20. As I mentioned,
the rest of 44net has tunnels to HamWAN, so this dumb router is out of
the picture.

Tom KD7LXL

On Wed, Apr 9, 2014 at 2:03 PM, Dean Gibson AE7Q <hamwan at ae7q.com> wrote:
> Via my external host (directly on the Internet):
>
>>ping ampr.org
> PING ampr.org (44.0.0.1) 56(84) bytes of data.
> 64 bytes from ampr.org (44.0.0.1): icmp_seq=0 ttl=45 time=93.5 ms
>
> Through the HamWAN radio:
>
>>ping ampr.org
> PING ampr.org (44.0.0.1) 56(84) bytes of data.
> From 44.24.240.135 icmp_seq=0 Destination Host Unreachable
>
> A routing loop???:
>
>>traceroute ampr.org
> traceroute to ampr.org (44.0.0.1), 30 hops max, 38 byte packets
>  1  5shpn-1_ext (192.168.3.251)  0.411 ms  0.237 ms  0.228 ms
>  2  44.24.240.161 (44.24.240.161)  127.458 ms  23.392 ms  74.152 ms
>  3  44.24.240.136 (44.24.240.136)  55.588 ms  28.191 ms  4.444 ms
>  4  44.24.242.7 (44.24.242.7)  131.127 ms  434.037 ms  1232.351 ms
>  5  44.24.242.16 (44.24.242.16)  74.558 ms  347.674 ms  517.633 ms
>  6  gi1-0-149-sea1.threshinc.com (209.189.196.65)  775.778 ms  380.374 ms
> 529.840 ms
>  7  ge0-1-thbr03.threshinc.net (209.189.201.195)  338.481 ms  264.768 ms
> 277.434 ms
>  8  tge2-2.fr3.sea2.llnw.net (206.81.80.99)  368.613 ms  253.695 ms  502.565
> ms
>  9  tge2-2.fr3.sjc.llnw.net (69.28.171.145)  1324.350 ms  1615.159 ms
> 139.687 ms
> 10  ve5.fr4.sjc.llnw.net (69.28.171.210)  165.213 ms  299.371 ms  167.546 ms
> 11  paix-px1--limelight-10ge.cenic.net (198.32.251.193)  197.806 ms
> 3515.491 ms calren-cenic.paix.net (198.32.176.33)  204.395 ms
> 12  dc-svl-px1--paix-px1-ge.cenic.net (137.164.47.173)  247.990 ms  358.917
> ms *
> 13  * * *
> 14  * dc-lax-core2--svl-core1-10ge.cenic.net (137.164.47.24)  433.794 ms
> 227.051 ms
> 15  dc-lax-core1--lax-core2-10ge-4.cenic.net (137.164.46.68)  289.399 ms
> 266.228 ms  303.996 ms
> 16  dc-riv-core1--lax-core1-10ge-4.cenic.net (137.164.46.103)  287.258 ms
> 299.758 ms  301.851 ms
> 17  dc-sdg-agg1--riv-core1-10ge-2.cenic.net (137.164.47.15)  572.338 ms
> 391.259 ms  148.496 ms
> 18  dc-ucsd-1--sdg-agg1.cenic.net (137.164.23.54)  453.700 ms  149.203 ms
> 375.147 ms
> 19  * * *
> 20  * * *
> 21  dc-sdg-agg1--riv-core1-10ge-2.cenic.net (137.164.47.15)  448.335 ms
> 385.200 ms  486.918 ms
> 22  dc-ucsd-1--sdg-agg1.cenic.net (137.164.23.54)  204.232 ms *  249.699 ms
> 23  * * *
> 24  * * *
> 25  * * *
> 26  * * *
> 27  * * *
> 28  * * *
> 29  * * *
> 30  * * *
>
> Probably not a HamWAN problem ... just commenting.
>
> -- Dean
>
>
> _______________________________________________
> PSDR mailing list
> PSDR at hamwan.org
> http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
>