Am I missing something? So far I have not seen anyone use the 44 block for their mesh network. Is there a reason for this?

The 44.0.0.0/8 subnet, otherwise known as the AMPRNet, is a public address space and is in large part already allocated to other hams and regions.  As a public address space, these addresses are routable from the Internet, as are all other public addresses, and this is their purpose.

On the other hand, any mesh is a private network which is not dependent upon Internet routability.  The 10.0.0.0/8 address space is already set aside for this purpose, does not conflict with existing Internet addresses, and is the only IPv4 space large enough to adequately allow for automatic address assignment on a large scale.  The ability to connect to the Internet is generally considered a desirable thing, and to do so one must play by the rules of the Internet.

73

ad5oo

How do you plan on handling your routing table? Who will you tunnel to on the 44.0.0.0/8 network so traffic is routing in both directions?

First Answer

For the time being I am assuming I will not be putting anything outside of the private ip address ranges 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 onto HSMM-MESH, that being said the HSMM-MESH would be a isolated network. I don't see a need for NAT in an HSMM-MESH other then it would require less configuration.

I would rather have routing via OSPF routing tables and each node assigned its only private IP address space for devices be hide at. This would require assignment of IP address from some central authority and I do like the idea of wireless mesh nodes being compatible from different home areas with no IP address conflicts(mainly in the event of an Emergency). So the Central Authority could be a dynamic Server(s) or a national/global authority. I personally hate NAT. 

This authority is already in place for the 44.0.0.0/8 space, However that is for internet routable traffic, which would be highly use for in an emergency event. Almost as if the Node themselves could offer two modes of operation normal/private and emergency/public.

With maybe different Central Authority for both for national/global ip address assignment, one for private non-internet/normal mode and one for emergency/public internet mode.

I would also like to state that I am very open to my ideas being wrong, as far as I know it might already be done this way, most likely however it is done now is for a VERY GOOD REASON. At this point I am very much a outsider just starting to look into HSMM. 

If you have gone to the effort of being allocated a subnet within the 44.0.0.0/8 space and having made the arrangements with your ISP to have that traffic routed to you, then by all means set up your network to work in that manner.  Keep in mind though that you have taken on a lot of manual configuration and administration, and you are running what is essentially a private mesh.  Nobody else could come within RF range of your mesh and expect to have their node work with yours without it being pre-configured to do so.  HSMM-MESH is not intended to bring inbound Internet access to the mesh, nor is it intended to require nodes to have a specific manual configuration to be able to use the mesh.  Putting a mesh on 44 cannot meet those goals, and there are other mesh network implementations that would be better suited for this purpose.  If you believe that the HSMM-MESH firmware really is the best tool for your job, feel free to use it but please change your SSID along with all the other settings and software that will have to be modified to make a 44 mesh work.

73
ad5oo

Sorry, I should have made it clear that my response was directed toward KE5SWU who asked the original question.  I see that you (KF7RMM) have other intentions for the 44 subnet.  If you have a 44 address, using it on the WAN side of a node is fine, but not having done that myself I do not know how that is done from an internet routing perspective.

73
ad5oo

44.x.x.x Amateur IP space was reserved at a time prior to TCP/IP was generally available. 

If you look at the way it is managed/routed you would be wise to avoid it for HSMM. We have outgrown its usefulness so just use the IP space you get from your Internet provider. Start thinking about IPv6 and VPNs instead.