Re: [44net] Routing of 44.0.0.0/8 how are routes announced to users?

Hi Brian Thank you for your quick explanations. Ok I now understand that routing is not just nice and easy done by routing protocols as in the internet but a hand-made error prone mesh :-) Yes I am. Well, so the DNS PTR filter would only affect packets transfered across gateways between hamnet and the internet. So any clue, why I can not reach parts from the hamnet 44.0.0.0/8 space from my true hamnet ip address: 44.142.162.123? Mainly the 'primary' DNS Server of ampr.org which I assumed should be reachable from everywhere within hamnet: traceroute to 44.0.0.1 (44.0.0.1), 30 hops max, 60 byte packets 2 mikrotik-hamnet.woody.ch (192.168.57.243) 4.584 ms 4.605 ms 4.585 ms 3 rf0.am-32.hb9am.ch.ampr.org (44.142.162.97) 12.475 ms 12.477 ms 18.788 ms 4 bb-hb9am-30.db0wbd.ch.ampr.org (44.224.90.81) 18.827 ms 24.174 ms 24.165 ms 5 wan-db0wbd.hc.r1.ampr.org (44.148.240.45) 62.922 ms 70.345 ms 72.729 ms 6 dc1-dc2.hc.r1.ampr.org (44.148.255.253) 95.661 ms 93.691 ms 102.363 ms 7 wan-db0gw.db0fhn.ch.ampr.org (44.224.122.2) 108.112 ms 111.090 ms 117.816 ms 8 db0fhn.ch.ampr.org (44.130.60.100) 122.348 ms 116.826 ms 121.290 ms 9 * * * 10 * * * 11 * * * (Forget about the local IP 192.168.57.243, this is the LAN side, the packets get source nated to 44.142.162.123) I mentioned DMR, but as I also run an APRS i-Gate I wanted to have it connect to the APRS-IS Server within Hamnet: db0alg.ampr.org 3 rf0.am-32.hb9am.ch.ampr.org (44.142.162.97) 19.117 ms 24.044 ms 24.063 ms 4 br0.am-33.hb9am.ch.ampr.org (44.142.162.67) 26.680 ms 28.756 ms 28.985 ms 5 eth3.zrh-am.hb9zrh.ch.ampr.org (44.142.255.177) 61.952 ms 82.993 ms 106.007 ms 6 * * * 7 * * * 8 * * * Same Problem, it's not reachable within hamnet. So is this an issue I have to look at with the local swiss admins, or is this common, that there are local, non interconnected regions within hamnet? Or is this a result of the manual routing mesh? Benoît HB9EUE