[HamWAN PSDR] Connecting to 44.0.0.1 (or not)
Bart Kus
me at bartk.us
Wed Apr 9 14:58:07 PDT 2014
This really should get fixed. Here are a couple traces from Seattle-ER1
to 44.0.0.1:
[eo at Seattle-ER1] > /tool traceroute address=44.0.0.1
src-address=209.189.196.68
# ADDRESS LOSS SENT LAST AVG BEST
WORST STD-DEV STATUS
1 209.189.196.65 0% 10 1.9ms 0.8 0.4
1.9 0.5
2 209.189.202.195 0% 10 0.7ms 73.1 0.4
261 108.6
3 206.81.80.99 0% 10 0.7ms 5.1 0.5
10.7 3.9
4 69.28.171.145 0% 10 28ms 26.6 20
38.1 5.2
5 69.28.171.210 0% 10 22.8ms 21.4 18.6
31.9 3.9
6 198.32.176.33 0% 10 21.6ms 19.5 19.1
21.6 0.7
7 137.164.47.19 0% 10 21.4ms 24.1 21.4
29 2
8 137.164.46.67 0% 10 25.1ms 25.1 23.6
27.1 0.9
9 137.164.46.244 0% 10 34.7ms 33.5 32.4
35.6 1.2
10 137.164.47.15 0% 10 39.4ms 39.7 39.3
41.5 0.6
11 137.164.23.54 0% 10 39.7ms 40.2 39.5
43.2 1
12 132.239.254.163 0% 10 40.5ms 41.5 39.7
49.1 2.7
13 132.239.255.131 0% 10 39.6ms 40.2 39.6
43.1 1
14 44.0.0.1 10% 10 39.7ms 39.9 39.6
40.5 0.3
[eo at Seattle-ER1] > /tool traceroute address=44.0.0.1
src-address=44.24.242.22
# ADDRESS LOSS SENT LAST AVG BEST
WORST STD-DEV STATUS
1 209.189.196.65 0% 5 0.7ms 1.3 0.5
2.5 0.7
2 209.189.201.195 0% 5 3.5ms 1.5 0.5
3.5 1.2
3 206.81.80.99 0% 4 0.4ms 4.1 0.4
8.1 3.5
4 69.28.171.145 0% 4 25.7ms 24.7 19.6
29.6 3.6
5 69.28.171.210 0% 4 34.7ms 25.3 21.5
34.7 5.5
6 198.32.176.33 0% 4 19.5ms 20.4 19.3
23.2 1.6
7 137.164.47.19 0% 4 23.7ms 23.6 21.9
25.4 1.3
8 137.164.46.1 0% 4 24.4ms 26.3 24.4
27.5 1.2
9 137.164.46.248 0% 4 36.1ms 33.8 32.1
36.1 1.5
10 137.164.47.111 0% 4 42.9ms 40.3 39.1
42.9 1.6
11 137.164.23.54 0% 4 41.2ms 45.8 39.8
61.6 9.1
12 100% 4 timeout
13 100% 4 timeout
14 100% 4 timeout
15 100% 4 timeout
16 100% 4 timeout
The only difference is the source address being used.
--Bart
On 04/09/2014 02:32 PM, Tom Hayward wrote:
> 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
>>
> _______________________________________________
> PSDR mailing list
> PSDR at hamwan.org
> http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.hamwan.net/pipermail/psdr/attachments/20140409/3a940a63/attachment.html>
More information about the PSDR
mailing list