Hi All,
following the recent discussions on this list I like to remind that there are really active regions using net44. In preparation of the HAM RADIO in Friedrichshafen (www.hamradio-friedrichshafen.de/ham-en) I created an overview of such a region. Please find the "HAMNET Overview 2012" at http://db0fhn.efi.fh-nuernberg.de/doku.php?id=start&#hamnet
--- As one of the IP-coordinators for this region I'm very happy to be able to use 44/8 for the allocations. Two reasons for that:
* 44/8 will never clash with our radio amateurs private used RFC1918 addresses within 10/8, 172.16/12 or 192.168/16. They can fully integrate AMPR access into their LAN.
* I can easily adjust my firewall rules to distinguish between radio amateurs (44/8) and the rest of the internet. Discussions about CIDR makes me nervous :D
--- Currently I'm thinking about different tunnel mechanism for net44 and I don't know the answer :)
On one hand we have our stable system to distribute information about IP-ENCAP (protocol #4) tunnels to net44-routes by E-Mail, FTP or RIP. Routing information will be updated through the robot once a day. --> no realtime
On the other hand we have manual IP-ENCAP tunnels for our tunnels within the HAMNET (a part of the AMPRNet). We speak BGPv4 over these tunnels and get realtime routing information. --> no automatic tunnels
I don't know what would be the best for tunneling. Isn't there a proper mesh protocol? I did have a look at OpenNHRP, but it will not fit our needs regarding a simple, automatic, realtime capable solution.
--- I do like the posting from Hessu, OH7LZB, about the different technical solutions to do direct announcements on the Internet. Right questions to be answered... However at this stage I guess most AMPRNet-systems will not be able to directly communicate to net44-destinations with their own net44-ip-address.
73, Jann DG8NGN