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
Hello Everyone,
I'm helping out a local HAM getting an IPIP AMPR setup working but his
current AT&T Uverse / Pace s 5862ac unit doesn't seem to be playing
nicely. Yeah.. I know.. Shocking! Anyway, touter/NAT mode seems to
*only* want to forward TCP/UDP protocols (typical) and it's DMZPlus
feature mode seems to be breaking his Wifi network. As we maybe hack
with the DMZplus feature tomorrow, I was curious if there is anyone
willing to offer up a VPN connection to his Raspberry Pi as a Plab-B:
Looking through the archives, there was
http://wiki.ampr.org/index.php/AMPRNet_VPN but that link is 404. I know
there is also the http://wiki.ampr.org/wiki/AMPRNet_VPN link but I know
other HAMs are/were offering less complicated setups. I can help him
setup any offering be it IPSEC, SSL-VPN, etc. He's not looking for any
sort of performance.. just general IPIP access to play around, etc. at
the moment.
If already hosting or you're willing to host a solution, let me know.
Thanks!
--David
KI6ZHD
All the examples I have found have a static public ip, is there a way to do it with a dynamic public ip, my ISP does not assign statics to residential customers.
cantantes laudat orbis terrarum
I have followed the directions in http://lz4ny.eu/en/amprnet-44-rip/ to setup my GW, but all I get when I run ampr-ripd is the following
root@thor:/home/w0kcf# ampr-ripd -d -i tunl0
Using gateway 192.168.1.1 for direct 44net endpoints via interface enp0s18.
Waiting for RIPv2 broadcasts...
Network configuration is as follows
w0kcf@thor:~$ ifconfig
enp0s10 Link encap:Ethernet HWaddr 00:14:6c:81:ff:fe
inet addr:44.26.1.80 Bcast:44.26.1.95 Mask:255.255.255.240
inet6 addr: fe80::214:6cff:fe81:fffe/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16335 errors:0 dropped:10870 overruns:0 frame:0
TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1273233 (1.2 MB) TX bytes:6874 (6.8 KB)
enp0s18 Link encap:Ethernet HWaddr 00:13:8f:7a:c8:aa
inet addr:192.168.1.9 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:8fff:fe7a:c8aa/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:23028 errors:0 dropped:0 overruns:0 frame:0
TX packets:17964 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6155448 (6.1 MB) TX bytes:2789754 (2.7 MB)
What am I missing?
73
Kevin W0KCF
