24 Feb
2018
24 Feb
'18
6:58 p.m.
Hi Brian
Thank you for the quick reply.
But I fear they don't explain the routing issue I see.
If my country coordinator did not choose to announce it's /16, it is
routed via UCSD.
At the moment, my Mikrotik connected to the HAMNET AP on the next hill,
is getting: 44.142.162.123 via DHCP.
So if I got that right, this IP should be reachable via UCSD for the
'internet' world:
traceroute to 44.142.162.123 (44.142.162.123), 64 hops max, 40 byte packets
1 prt-cbl-sw1-vlan-13-0.gw.imp.ch (157.161.1.1) 1.947 ms 1.693 ms 1.273 ms
2 prt-cbl-core1-ve-255.gw.imp.ch (157.161.254.5) 0.737 ms 0.72 ms 0.774 ms
3 swissix.zrh2.llnw.net (91.206.52.217) 10.473 ms 10.431 ms 36.897 ms
4 tge1-1.fr3.mrs1.llnw.net (87.248.194.221) 16.802 ms 16.758 ms 16.781 ms
5 lag34.fr3.cdg1.llnw.net (68.142.88.62) 18.134 ms 18.146 ms 18.116 ms
6 lag20.fr3.iad.llnw.net (68.142.88.48) 93.476 ms 93.568 ms 98.834 ms
7 lag33.fr3.atl1.llnw.net (68.142.88.153) 115.251 ms 115.383 ms 115.225 ms
8 lag23.fr3.dal.llnw.net (68.142.88.137) 135.555 ms 135.661 ms 135.636 ms
9 lag10.fr3.phx3.llnw.net (68.142.88.129) 154.628 ms 154.773 ms 154.6 ms
10 tge1-1.fr3.aza1.llnw.net (69.164.62.16) 154.898 ms 154.856 ms 154.785 ms
11 lag25.fr3.lax.llnw.net (68.142.88.168) 167.615 ms 167.707 ms 167.612 ms
12 198.32.251.189 (198.32.251.189) 159.841 ms 159.864 ms 159.75 ms
13 137.164.11.25 (137.164.11.25) 161.957 ms 137.164.11.23 (137.164.11.23) 161.043 ms
160.964 ms
14 dc-sdg-agg4--tus-agg3-100ge.cenic.net (137.164.11.9) 162.512 ms 137.164.11.11
(137.164.11.11) 162.053 ms dc-sdg-agg4--tus-agg3-100ge.cenic.net (137.164.11.9) 162.323
ms
15 dc-ucsd-1--sdg-agg4.cenic.net (137.164.23.54) 161.835 ms 161.855 ms 161.852 ms
16 nodem-core-6807-vlan2767-gw.ucsd.edu (132.239.254.61) 162.085 ms 161.915 ms 162.061
ms
17 rci-nodem-p2p.ucsd.edu (132.239.254.177) 162 ms 162.759 ms 163.389 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
Noe, it isn't. From my point of view, this would be OK, as the hamnet
links could be very slow packetradio links and you do not want to
expose them to the bad things on the internet which constantly scan the
whole ip range. :-)
But then, why not just announce the /16 which are reachable via
internet? It's not that a bad pollution of the routing table as routing
single /24s.
And also the other way round, why am I not able to reach the ampr.org
primary DNS, over hamnet?
How, as a hamnet 'user' do I know which hamnet destinations are
reachable via internet and which ones via internet? I would need to run
a routing protocol for that and establish peerings, from a dynamic
IP?!?, but this is something the 'normal' user would be unable to cope
with and in my point of view, not the task of the user.
Well, my goal was initially to connect my DMR hotspot via HamNet so it
would work independently of my internet connection, but if the DMR
Master's HAMNET IP Address I want to connect to is not reachable via
hamnet, that does not make much sense.
73 Benoit HB9EUE