25 Feb
2018
25 Feb
'18
4:25 a.m.
Benoit,
Routing between HAMNET (which is not reachable from the Internet) and 44net
hosts that are reachable via the Internet is always tricky. And I need some
more details to figure out what is going wrong, probably at the
international HAMNET routing node at DB0FHN.
To take a closer look at the situation, contact me directly at
hb9ctb(a)bluewin.ch
73 de Markus HB9CTB
Markus Müller HB9CTB
Coordinator HAMNET/44net IP Adresses Switzerland
-----Ursprüngliche Nachricht-----
Von: 44Net [mailto:44net-bounces+hb9ctb=bluewin.ch@mailman.ampr.org] Im
Auftrag von Benoit Panizzon
Gesendet: Samstag, 24. Februar 2018 10:10
An: AMPRNet working group
Betreff: [44net] Routing of 44.0.0.0/8 how are routes announced to users?
Dear List
I'm pretty newly connected to hamnet, and also work at an ISP.
I always assumed 44.0.0.0/8 would not be announced to the internet, but only
routed privately on hamnet.
Now I see routing issues I don't quite understand as for me this looks like
routing is completely broken...
On the internet core router I see that 44.0.0.0/8 is being announced by
AS7377 (UCSD).
But IP Addresses from the swiss HamNet range are not reachable via AS7377.
So what is the point announcing the whole range to the internet? There is no
'more specific' route to 44.142.200.1
On the other hand I cannot reach parts of hamnet via hamnet. Take for
example the Primary DNS of ampr.org:
ampr.org. 3600 IN SOA ampr.org.
ampr.org has address 44.0.0.1
1 gateway (157.161.57.65) 2.947 ms 2.887 ms 2.847 ms
2 mikrotik-hamnet.woody.ch (192.168.57.243) 4.937 ms 4.920 ms 4.887 ms
3 rf0.am-32.hb9am.ch.ampr.org (44.142.162.97) 21.810 ms 24.858 ms
29.860 ms
4 bb-hb9am-30.db0wbd.ch.ampr.org (44.224.90.81) 29.847 ms 32.792 ms
32.771 ms
5 wan-db0wbd.hc.r1.ampr.org (44.148.240.45) 78.907 ms 81.925 ms 84.438
ms
6 dc1-dc2.hc.r1.ampr.org (44.148.255.253) 97.808 ms 98.107 ms 113.973
ms
7 wan-db0gw.db0fhn.ch.ampr.org (44.224.122.2) 113.986 ms 113.149 ms
118.384 ms
8 db0fhn.ch.ampr.org (44.130.60.100) 126.890 ms 118.628 ms 137.776 ms
9 * * *
My Gateway has a default route to the internet and a static route for
44.0.0.0/8 pointing to my WLAN Link to a 'public' Hamnet AP.
So what is the point of having sort of a split-brain situation on the
44.0.0.0/8 hamnet ip range?
I 'see' ospf packets on the WLAN link, but they only seem announce the local
routes withing the swiss part of hamnet, not the global routes.
Sort of makes sense, as you probably would run bgp to interconnect the
different hamnet as numbers.
So do I need to get an own hamnet as number? As a User?!?
Or what mechanism is there supposed to be to tell a user which hamnet ip
ranges are reachable via internet and which ones are reachable via hamnet.
73
-Benoit- / HB9EUE
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net