Hello Benoit,
Am 24.02.2018 um 10:09 schrieb Benoit Panizzon panizzon@woody.ch:
Dear List
I'm pretty newly connected to hamnet, and also work at an ISP.
You should better ask your local community about your problems and questions. No one in america, russia or china will be able to answer you question.
I always assumed 44.0.0.0/8 would not be announced to the internet, but only routed privately on hamnet.
That's only partial true.
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).
Yes, since the 1980's.
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
connectivity. For the users who like be reachable. ucsd.edu knows the path to your 44.142.200.1 via the correspondent ipip-gateway. He may filter traffic from the internet in order to protect you from non-ham-traffic and other harmful things.
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 * * *
Interesting: Your local dns server maps the official reverse lookup (db0fhn.as64664.de.ampr.org) under a ch.ampr.org domain.
44.0.0.1 is only reachable from a source address in 44/8, if this address has a reverse lookup. Perhaps it's part of the concept, that ucsd.edu filters incoming internet traffic for unassigned 44-destinations. Unfortunately, it affects the dns resolving.
You said, your IP is 44.142.200.1 ? That IP does not have a PTR record.
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.
Common setup.
So what is the point of having sort of a split-brain situation on the 44.0.0.0/8 hamnet ip range?
No split-brain. Unfortunately, it's a filter that affects you.
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.
It's a local configuration of your hotspot. They may speak ospf. Ask them what's it worth for.
Sort of makes sense, as you probably would run bgp to interconnect the different hamnet as numbers.
Yes, the hamnet routers speak bgp to each other.
So do I need to get an own hamnet as number? As a User?!?
No. In no hamnet area I know.
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.
There's no such mechanism.
vy 73, - Thomas dl9sau